Locking system using wireless bridge

ABSTRACT

A locking system includes a server, an electronic locking mechanism, and a controller associated with a user. The controller is configured to detect the electronic locking mechanism and acquire lock data therefrom, and transmit the lock data to the server. The server, absent any interaction from the user, is configured to receive the lock data for the electronic locking mechanism, register the electronic locking mechanism to the user, and transmit an access credential for accessing the electronic locking mechanism to a user device associated with the user. The electronic locking mechanism is configured to receive the access credential directly from the user device or indirectly from the user device through the controller and make an access decision based on the access credential, independent of the server.

CROSS-REFERENCE TO RELATED PATENT APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/530,960, filed Aug. 2, 2019, which claims the benefit of U.S.Provisional Application No. 62/714,273, filed Aug. 3, 2018, both ofwhich are incorporated herein by reference in their entireties.

BACKGROUND

Electronic entry door features, such as electronic door locks (e.g.,push button, biometric sensor, RFID reader), intercoms, cameras, motionsensors, and lighting, have been provided as modular, battery poweredsolutions for installation on or near an entry door, to provideadditional security and convenience, and may, for example, provide forremote communication with a user (e.g., homeowner, business owner,resident, or employee), for example, through wireless communication(e.g., Wi-Fi or cellular) with the user's cell phone, tablet, orcomputer.

SUMMARY

One embodiment relates to a locking system. The locking system includesa server, an electronic locking mechanism, and a controller associatedwith a user. The controller is configured to detect the electroniclocking mechanism and acquire lock data therefrom, and transmit the lockdata to the server. The server, absent any interaction from the user, isconfigured to receive the lock data for the electronic lockingmechanism, register the electronic locking mechanism to the user, andtransmit an access credential for accessing the electronic lockingmechanism to a user device associated with the user. The electroniclocking mechanism is configured to receive the access credentialdirectly from the user device or indirectly from the user device throughthe controller and make an access decision based on the accesscredential, independent of the server.

Another embodiment relates to a locking system. The locking systemincludes a server and a controller associated with a user. Thecontroller is configured to detect an electronic locking mechanism andacquire lock data therefrom, and transmit the lock data to the server.The server, absent any interaction from the user, is configured toreceive the lock data for the electronic locking mechanism, register theelectronic locking mechanism to the user, and transmit an accesscredential for accessing the electronic locking mechanism to a userdevice associated with the user.

Still another embodiment relates to a method for automaticallyregistering an electronic locking mechanism. The method includesdetecting, by a controller, the electronic locking mechanism, whereinthe controller is associate with a user; acquiring, by the controller,lock data from the electronic locking mechanism; transmitting, by thecontroller, the lock data to a server; receiving, by the server, thelock data the electronic locking mechanism; registering, by the server,the electronic locking mechanism to the user; transmitting, by theserver, an access credential for accessing the electronic lockingmechanism to a user device associated with the user; receiving, by theelectronic locking mechanism, the access credential directly from theuser device or indirectly from the user device through the controller;and making, by the electronic locking mechanism, an access decisionbased on the access credential.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view of an integrated electronic door system withpower supplied to the door slab through electrical wiring in the core,according to an exemplary embodiment.

FIG. 2 is a schematic view of an integrated electronic door system withpower supplied to the door slab through electrical wiring in the core,according to another exemplary embodiment.

FIG. 3 is a schematic view of an integrated electronic door system withpower supplied to the door slab through electrical wiring in the core,according to another exemplary embodiment.

FIG. 4 is a schematic block diagram of an electronic control system foran integrated electronic control system having independently operableelectronic features, according to an exemplary embodiment.

FIG. 5 is a schematic view of an integrated electronic door system withpower supplied to the door slab through electrical wiring and acontroller in the core, according to another exemplary embodiment.

FIG. 6 is a schematic view of an integrated electronic door system withpower supplied to the door slab through electrical wiring and acontroller in the frame, according to another exemplary embodiment.

FIG. 7 is a schematic block diagram of an electronic control system foran integrated electronic control system having independently operableelectronic features, according to an exemplary embodiment.

FIG. 8 is a front view of a composite door with a portion removed toexpose the internal structure thereof, according to an exemplaryembodiment.

FIG. 9 is a side view of the door of FIG. 8; and

FIG. 10 is a cross-sectional view of the door of FIG. 9 showing theinternal structure of thereof.

FIG. 11 is a schematic block diagram of an electronic door system,according to an exemplary embodiment.

FIG. 12 is a schematic diagram of a door assembly of the electronic doorsystem of FIG. 11, according to an exemplary embodiment.

FIG. 13 is a schematic diagram of a door assembly of the electronic doorsystem of FIG. 11, according to another exemplary embodiment.

FIG. 14 is a block diagram of a wireless bridge of the door assembly ofFIGS. 12 and 13, according to an exemplary embodiment.

FIG. 15 is a block diagram of a locking system of the door assembly ofFIGS. 12 and 13, according to an exemplary embodiment.

FIG. 16 is a block diagram of a camera system of the door assembly ofFIGS. 12 and 13, according to an exemplary embodiment.

FIG. 17 is a block diagram of a controller of the door assembly of FIGS.12 and 13, according to an exemplary embodiment.

FIG. 18 is a block diagram of a door server of the electronic doorsystem of FIG. 11, according to an exemplary embodiment.

FIG. 19 is a block diagram of a camera server of the electronic doorsystem of FIG. 11, according to an exemplary embodiment.

FIG. 20 is a block diagram of a user device useable with the electronicdoor system of FIG. 11, according to an exemplary embodiment.

FIG. 21 is a schematic block diagram of a first communication processbetween components of the electronic door system of FIG. 11, accordingto an exemplary embodiment.

FIG. 22 is a schematic block diagram of a second communication processbetween components of the electronic door system of FIG. 11, accordingto an exemplary embodiment.

FIG. 23 is a schematic block diagram of a third communication processbetween components of the electronic door system of FIG. 11, accordingto an exemplary embodiment.

FIG. 24 is a schematic block diagram of a fourth communication processbetween components of the electronic door system of FIG. 11, accordingto an exemplary embodiment.

FIG. 25 is a schematic block diagram of a fifth communication processbetween components of the electronic door system of FIG. 11, accordingto an exemplary embodiment.

DETAILED DESCRIPTION

Before turning to the figures, which illustrate certain exemplaryembodiments in detail, it should be understood that the presentdisclosure is not limited to the details or methodology set forth in thedescription or illustrated in the figures. It should also be understoodthat the terminology used herein is for the purpose of description onlyand should not be regarded as limiting.

As utilized herein, the term “key” (e.g., device key, user key, bridgekey, cryptographic key, etc.) means a numeric or alphanumeric code,which, for example, may be a parameter used in a block cipher algorithmthat determines a forward cipher function. As utilized herein, the term“nonce” (e.g., handshake nonce, reply nonce, modified reply nonce, etc.)means a value that is used (e.g., only once) within a specified context.The terms “circuit” or “circuitry,” as utilized herein, connotehardware, software, or any combination thereof. In other words, aparticular circuit described herein may be implemented using hardwarecomponents, instructions stored on one or more computer-readable storagemedia that are executable by processing circuitry (e.g., amicroprocessor) to implement the associated functions described herein,or a combination of hardware and executable instructions. All suchimplementations are contemplated within the scope of the presentdisclosure.

Electronic Door Arrangements

As shown in FIGS. 8-10, fiberglass doors 10 typically include adoor-shaped solid (e.g., wooden) frame member 14, a polymeric foam-typecore 12 positioned within the frame member 14, a first or front doorskin 24 secured to a first side of the frame member 14, and a second orrear door skin 26 secured to a second side, opposite the first side, ofthe frame member 14. The front door skin 24 and the rear door skin 26may, for example, be formed as fiberglass reinforced compression moldedpanels prepared from a molding compound.

According to an exemplary embodiment, a composite (e.g., having afiberglass or foam filled frame) door assembly may be provided with oneor more electronic features integrated into the door and in wiredelectrical communication with the building's electrical system toprovide an integrated electronic (or “smart”) entry door solution,without the need for separate end user installation of one or moremodular electronic components.

While the electronic features and systems described herein may beintegrated into many types of doors, the foam filled cavity of acomposite fiberglass door facilitates incorporation of internalelectronic features within the door, without requiring extensivemachining or modification, as may be the case with a solid or monolithicdoor. Fiberglass doors typically include a door-shaped frame member(e.g., having wooden horizontal rails and vertical stiles), first andsecond fiberglass reinforced compression molded door skins secured toopposed first and second sides of the frame member, and a polymericfoam-type core (e.g., sprayed-in foam or cut block foam pieces)positioned between the door skins and within the frame member.

The door may include, within its foamed-in enclosure, electrical wiringfor one or more electronic features, with the electrical wiringextending through a hinged portion (e.g., a hinged edge, etc.) of thedoor and into the door jamb for connection with the electrical system ofthe building. Exemplary electrical connections between the door edge andthe door jamb, include, for example, electric transfer hinges (e.g.,Series 1100 electric hinge, manufactured by ACSI) and flexible conduits(e.g., CDL series “concealed door loop,” manufactured by Command AccessTechnologies).

In some embodiments, an electronic feature that is integral to the door,such as, for example, an electrically activated privacy window (asmanufactured, for example, by Innovative Glass Corp) may be connected toa building electrical system by electrical wiring integrated into acomposite door. As shown in FIG. 1, a door assembly, shown as doorsystem 100, includes an electrically-operated window (e.g., a glasswindow, etc.), shown as privacy window 120, connected to electricalwiring 110 routed through an interior core (e.g., a foam core, etc.),shown as core 106, of a slab, shown as door slab 105, to a flexibleconduit or electric transfer hinge 115 (as shown), and into a jamb,shown as door jamb 107. The electrical wiring 110 may be connecteddirectly or indirectly by external wiring 112 with a switch, shown ascontrol switch 190, installed, for example, on an interior building wallW, and connected with the building electrical system for user activationand deactivation of the privacy window 120. In other embodiments, thecontrol switch 190 is additionally or alternatively disposed directly ona rear surface of the door. In still other embodiments, the controlswitch 190 is in wireless communication (e.g., RFID, Bluetooth®,infrared, Wi-Fi, etc.) with the privacy window 120 for wireless controlof the privacy window 120, for example, through communication with atransceiver connected with the privacy window 120. In still otherembodiments, a transceiver connected with the privacy window 120 isconfigured to communicate with a smart phone or other computing device Cfor remote user control of the privacy window 120 using, for example, asmart phone application.

The electrical wiring 110 may be installed in the door slab 105 afterinstallation of the core 106, for example, into a slot or other suchcutout in the core 106. In one embodiment, a channel for the electricalwiring 110 may be drilled into the core 106 of a completed door,allowing for post-production installation of an integrated electronicsystem. Alternatively, in other embodiments, the electrical wiring 110may be installed in the door cavity prior to installation of the core106. For example, the electrical wiring 110 may be secured (e.g., taped)against an interior surface of at least one of the door skins, and thecore 106 may be subsequently installed (e.g., sprayed or inserted) overand/or around the electrical wiring 110.

In other embodiments, electronic features conventionally provided asmountable modular electronic components may be integrated into a doorslab, with integrated electrical wiring connecting the electronicfeatures to the building electrical system. As shown in FIG. 2, a doorassembly, shown as door system 200, includes an electrically-operatedlocking mechanism (e.g., an electronic door latch, an electronicdeadbolt, an electronic strike plate, etc.), shown as door lock 230, andsecurity camera, shown as camera 240, connected to electrical wiring 210routed through an interior core (e.g., a foam core, etc.), shown as core206, of a slab, shown as door slab 205, (installed either before orafter foam installation, as discussed above) to a flexible conduit orelectric transfer hinge 215 (as shown), and into a jamb, shown as doorjamb 207. The camera 240 may be fully enclosed within the door slab 205,with only a lens of the camera 240 exposed on a front surface of thedoor slab 205 (e.g., through an opening in the outer door skin). Thecamera may 240 be electrically connected with one or more sensorsintegrated into the door slab 205 (e.g., motion sensors, vibrationsensors) to activate the camera 240 when activity at the door system 200is detected.

To prevent contact between the electronic features and their electricalwiring connections with the core 206 (which may be flammable), theelectronic features and their wiring connections may be fully enclosedin housing members embedded in either or both of the outer door frame(e.g., the frame member 14, etc.) and the core 206.

As shown in FIG. 2, the electrical wiring 210 may be connected directlyor indirectly by external wiring 212 with a switch, shown as controlswitch 290, installed on an interior building wall W and connected withthe building electrical system for user operation of the door lock 230and the camera 240 (e.g., for specific control, for powering on/off,etc.). In other embodiments, the control switch 290 is additionally oralternatively disposed directly on a rear surface of the door slab 205.In still other embodiments, the control switch 290 is in wirelesscommunication (e.g., RFID, Bluetooth®, infrared, Wi-Fi, etc.) with anyof the electronic door features, for example, through communication witha transceiver connected with the corresponding electronic door feature.Additionally or alternatively, any one or more of the electronic doorfeatures may be provided with its own control system (e.g., anintegrated controller, etc.) for remote user control of the electronicfeature, for example, through wireless communication (e.g., Wi-Fi,cellular, Bluetooth, etc.) with a smart phone or other computing deviceC (e.g., a locally stored or web-based application). Either or both ofthe door lock 230 and the camera 240 may be provided with backup batteryunits, for example, for powered operation of the door lock 230 and/orthe camera 240 in the event of loss of power to the building.

In some integrated electronic door systems, electronic features mayrequire different electrical power supplies (e.g., high voltage and lowvoltage power supplies). As shown in FIG. 3, a door assembly, shown asdoor system 300, includes (i) an electrically-operated window (e.g., aglass window, etc.), shown as privacy window 320, connected to firstwiring, shown as high voltage electrical wiring 310 a, and (ii) anelectrically-operated locking mechanism, shown as door lock 330, and asecurity camera, shown as camera 340, connected to second, differentwiring, shown as low voltage electrical wiring 310 b. The high voltageelectrical wiring 310 a and the low voltage electrical wiring 310 b arerouted through an interior core (e.g., a foam core, etc.), shown as core306, of a slab, shown as door slab 305, (installed either before orafter foam installation, as discussed above) to a flexible conduit orelectric transfer hinge 315 (as shown), and into a jamb, shown as doorjamb 307, for connection with an external power source (e.g., a buildingpower source, etc.). The high voltage electrical wiring 310 a and thelow voltage electrical wiring 310 b may be connected directly orindirectly by external wiring 312 with a switch, shown as control switch390, installed on an interior building wall W and connected with thebuilding electrical system for user operation of one or more of theprivacy window 320, the door lock 330, and the camera 340 (e.g., forspecific control, for powering on/off, etc.). In other embodiments, thecontrol switch 390 is disposed directly on a rear surface of the doorslab 205. In still other embodiments, the control switch 390 is inwireless communication (e.g., RFID, Bluetooth®, infrared, Wi-Fi, etc.)with any of the electronic door features, for example, throughcommunication with a transceiver connected with the correspondingelectronic door feature.

Additionally or alternatively, any one or more of the electronic doorfeatures may be provided with its own control system (e.g., anintegrated controller, etc.) for remote user control of the electronicfeature, for example, through wireless communication (e.g., Wi-Fi,cellular, Bluetooth, etc.) with a smart phone or other computing deviceC (e.g., a locally stored or web-based application). Either or both ofthe door lock 330 and the camera 340 may be provided with backup batteryunits, for example, for powered operation of the door lock 330 and/orthe camera 340 in the event of loss of power to the building.Additionally or alternatively, an internal power supply, shown as backupbattery 395, may be integrated into the door slab 305 for connectionwith one or more of the electronic features of the door system 300 tosupply backup power to the electronic features in the event of buildingpower loss. In an exemplary embodiment, the backup battery 395 may beconfigured to supply only low voltage power to the corresponding lowvoltage electronic devices (e.g., the door lock 330, the camera 340,etc.) without powering high voltage electronic device(s) (e.g., theprivacy window 320, etc.). The backup battery 395 may be a rechargeablebattery connected with the building power supply and may be configuredto recharge when power to the building is operational and/or restored.

Referring now to FIG. 4, a schematic block diagram of an electroniccontrol system, shown as control system 400, for an integratedelectronic door (e.g., similar to the door system 300 of FIG. 3, etc.)is shown according to an exemplary embodiment. As shown in FIG. 4, thecontrol system 400, a privacy window 420, a door lock 430, and a camera440 are installed in a door slab 405 and connected by electrical wiring412 through a flexible conduit or electric transfer hinge 415 to anexternal power source and/or to an optional internal power supply, shownas battery backup 495, positioned within the door slab 405. As shown inFIG. 4, a light source (e.g., a LED light strip, etc.), shown aslighting element 450, is installed in a jamb, shown as door jamb 407,(e.g., above the door slab 405, etc.) and is connected by electricalwiring 411 to an external power source, shown as building power source408. The lighting element 450 and/or the camera 440 may be electricallyconnected with one or more sensors integrated into the door jamb 407and/or the door slab 405 (e.g., motion sensors, vibration sensors, etc.)to activate the lighting element 450 and/or the camera 440 when activityat the door slab 405 is detected.

As shown in FIG. 4, the door lock 430, the camera 440, and the lightingelement 450 are in wireless communication with a local Wi-Fi router,shown as router 497, for communication with a user interface I. As oneexample, the user interface I may be a voice controlled personalassistant (e.g., Amazon Echo® or the like) in wireless communicationwith the router 497, or a smartphone or other computing device C incommunication with the router via cloud service communication (e.g.,cloud service management by any one or more of the door manufacturerand/or the lock, camera, and/or lighting element provider). The privacywindow 420 is in wireless communication (e.g., Bluetooth®, Wi-Fi, etc.)with a switch, shown as control switch 490, for local user control ofthe privacy window 420 and/or the lighting element 450.

In still other embodiments, an electronic door system may include anintegrated controller (e.g., a control board, a control system, etc.)embedded in a composite door for integrated, single-source control of aplurality of electronic door features. As shown in FIG. 5, a doorassembly, shown as door system 500, includes an electrically-operatedwindow (e.g., a glass window, etc.), shown as privacy window 520, anelectrically-operated locking mechanism, shown as door lock 530, and asecurity camera, shown as camera 540, connected by first wiring, shownas high voltage electrical wiring 510 a, and second wiring, shown as lowvoltage electrical wiring 510 b to a controller, shown as control board580, respectively. The control board 580 is connected to (i) externalwiring, shown as external electrical wiring 512, and (ii) the highvoltage electrical wiring 510 a and the low voltage electrical wiring510 b routed through an interior core (e.g., a foam core, etc.), shownas core 506, of the door slab 505 (installed either before or after foaminstallation, as discussed above) to an electric transfer hinge orflexible conduit 515 (as shown), and into a jamb, shown as door jamb507, for connection with an external power source (e.g., a buildingpower source, etc.). As shown in FIG. 5, the electrical wiring (e.g.,the high voltage electrical wiring 510 a, the low voltage electricalwiring 510 b, the external electrical wiring 512, etc.) is connected(directly or indirectly) with a switch, shown as control switch 590,installed on an interior building wall W and connected with the buildingelectrical system for user operation of one or more of the privacywindow 520, the door lock 530, and the camera 540 (e.g., for specificcontrol, for powering on/off, etc.). In other embodiments, the controlswitch 590 is additionally or alternatively disposed directly on a rearsurface of the door slab 505. In still other embodiments, the controlswitch 590 is in wireless communication (e.g., RFID, Bluetooth®,infrared, Wi-Fi, etc.) with any of the electronic door features, forexample, through communication with a transceiver connected with thecorresponding electronic door feature.

The control board 580 may be provided with a wireless transceiver forwireless communication (e.g., Wi-Fi, cellular, Bluetooth, etc.) betweenany one or more of the installed electronic features and a smart phoneor other computing device C (e.g., using a locally stored or web-basedapplication). Additionally or alternatively, any one or more of theinstalled electronic features may be provided with their own controlsystems (e.g., an integrated controller, etc.) for remote user controlof the electronic feature, for example, through wireless communication(e.g., Wi-Fi, cellular, Bluetooth, etc.) with a smart phone or othercomputing device C (e.g., using a locally stored or web-basedapplication). Either or both of the door lock 530 and the camera 540 maybe provided with backup battery units, for example, for poweredoperation of the door lock 530 and/or the camera 540 in the event ofloss of power to the building. Additionally or alternatively, aninternal power supply, shown as backup battery 595, may be integratedinto the door slab 505 for connection with one or more of the electronicfeatures of the door system 500 to supply backup power to the electronicfeatures in the event of building power loss. In an exemplaryembodiment, the backup battery 595 is configured to supply only lowvoltage power to the corresponding low voltage electronic devices (e.g.,the door lock 530, the camera 540, etc.) without powering the highvoltage electronic device(s) (e.g., the privacy window 520, etc.). Thebackup battery 595 may be a rechargeable battery connected with thebuilding power supply and may be configured to recharge when power tothe building is operational and/or restored.

In other embodiments, a composite door may include electrical featuresand wiring embedded or otherwise disposed in an outer frame portion(e.g., the frame member 14, etc.) of the door such that a door may beassembled from a complete, electronics-integrated door frame member, forexample, to reduce door assembly time. As shown in FIG. 6, a doorassembly, shown as door system 600, includes an electrically-operatedwindow (e.g., a glass window, etc.), shown as privacy window 620, anelectrically-operated locking mechanism, shown as door lock 630, and asecurity camera, shown as camera 640, connected by first wiring, shownas high voltage electrical wiring 610 a, and second wiring, shown as lowvoltage electrical wiring 610 b, to a controller, shown as control board680, respectively. The control board 680 is connected to (i) externalwiring, shown as electrical wiring 612, and (ii) the high voltageelectrical wiring 610 a and the low voltage electrical wiring 610 brouted through an interior core (e.g., a foam core, etc.), shown as core606, of the door slab 605 (installed either before or after foaminstallation, as discussed above) to an electric transfer hinge orflexible conduit 615 (as shown), and into a jamb, shown as door jamb607, for connection with an external power source (e.g., a buildingpower source, etc.). The electrical wiring 610 a, 610 b, 612 is routedthrough channels in a door frame member (e.g., like the frame member 14;a through hole drilled or otherwise formed in the upper door rail, andthe inner and outer door stiles; etc.), shown as frame 601. The camera640 is retained in a first modular housing, shown as camera housing 641,received in a cavity in an upper edge of an upper door rail of the frame601 with a lens of the camera 640 aligned with an aperture in the doorslab 605 (e.g., an outer door skin thereof, etc.). The control board 680is retained in a second modular housing, shown as a controller housing681, received in the upper edge of the upper door rail of the frame 601.In other embodiments, the controller housing 681 is otherwise positionedwithin the frame 601 (e.g., received in the outer edge of one of thedoor stiles, etc.). The housing enclosures may protect the circuitry ofthe control board 680 and/or the camera 640, and their electrical wiringconnections, from contact with the core 606 (e.g., which may beconstructed from flammable material, etc.).

As shown in FIG. 6, the electrical wiring (e.g., the high voltageelectrical wiring 510 a, the low voltage electrical wiring 510 b, theexternal electrical wiring 512, etc.) is connected (directly orindirectly) with a switch, shown as control switch 690, installed on aninterior building wall W and connected with the building electricalsystem for user operation of one or more of the privacy window 620, thedoor lock 630, and the camera 640 (e.g., for specific control, forpowering on/off, etc.). In other embodiments, the control switch 690 isadditionally or alternatively disposed directly on a rear surface of thedoor slab 605. In still other embodiments, the control switch 690 is inwireless communication (e.g., RFID, Bluetooth®, infrared, Wi-Fi, etc.)with any of the electronic door features, for example, throughcommunication with a transceiver connected with the correspondingelectronic door feature.

The control board 680 may be provided with a wireless transceiver forwireless communication (e.g., Wi-Fi, cellular, Bluetooth, etc.) betweenany one or more of the installed electronic features and a smart phoneor other computing device C (e.g., using a locally stored or web-basedapplication). Additionally or alternatively, any one or more of theinstalled electronic features may be provided with their own controlsystems (e.g., an integrated controller, etc.) for remote user controlof the electronic feature, for example, through wireless communication(e.g., Wi-Fi, cellular, Bluetooth, etc.) with a smart phone or othercomputing device C (e.g., using a locally stored or web-basedapplication). Either or both of the door lock 630 and the camera 640 maybe provided with backup battery units, for example, for poweredoperation of the door lock 630 and/or the camera 640 in the event ofloss of power to the building. Additionally or alternatively, aninternal power supply, shown as backup battery 695, may be integratedinto the door slab 605 for connection with one or more of the electronicfeatures of the door system 600 to supply backup power to the electronicfeatures in the event of building power loss. In an exemplaryembodiment, the backup battery 695 may be configured to supply only lowvoltage power to the corresponding low voltage electronic devices (e.g.,the door lock 630, the camera 640, etc.) without powering the highvoltage electronic device(s) (e.g., the privacy window 620). The backupbattery 695 may be a rechargeable battery connected with the buildingpower supply and may be configured to recharge when power to thebuilding is operational and/or restored. Like the control board 680, thebackup battery 695 may be enclosed in a third housing installed in theframe 601, for example, to facilitate installation, and/or to provide afire safe enclosure for the backup battery 695 and its wiringconnections.

Referring now to FIG. 7, a schematic block diagram of an electroniccontrol system, shown as control system 700, for an integratedelectronic door (e.g., similar to the door system 600 of FIG. 6, etc.)is shown according to an exemplary embodiment. As shown in FIG. 7, thecontrol system 700, a privacy window 720, a door lock 730, and a camera740 are installed in a door slab 705 and connected by electrical wiringto a controller, shown as control board 780, which is connected byelectric wiring 712 through an electric transfer hinge 715 to anexternal power source, and to an optional internal power supply, shownas backup battery 795, disposed within the door slab 705. As shown inFIG. 7, a light source (e.g., a LED light strip, etc.), shown aslighting element 750, is installed in a jamb, shown as door jamb 707,(e.g., above the door slab 705, etc.) and is connected by electricalwiring 711 to an external power source, shown as building power source708.

The control board 780 is in wireless communication with a local Wi-Firouter, shown as router 797, for communication with a user interface I.As one example, the user interface I may be a voice controlled personalassistant (e.g., Amazon Echo® or the like) in wireless communicationwith the router 797, or a smartphone or other computing device C incommunication with the router via cloud service communication (e.g.,cloud service management by any one or more of the door manufacturerand/or the lock, camera, and/or lighting element provider). The privacywindow 720 may be in wireless communication (e.g., Bluetooth®) with awall mounted control switch 790 for local user control of the privacywindow 720.

Electronic Door System

According to the exemplary embodiment shown in FIG. 11, a door system(e.g., a smart door system, etc.), shown as electronic door system 1000,includes a door assembly, shown as electronic door assembly 1100, (i)electrically coupled to a first power source (e.g., a mains powersupply, a building power system, etc.), shown as external power source1602, and (ii) communicably coupled to (a) an intermediary device, shownas wireless router 1600, (b) one or more user devices (e.g., asmartphone, a mobile phone, a cell phone, a tablet, a laptop, acomputer, a smartwatch, a smartcard, a keycard, etc.), shown as userdevices 1900, directly and/or indirectly via the wireless router 1600,and (c) one or more remote servers, shown as door server 1700 and cameraserver 1800, via the wireless router 1600 and/or the user devices 1900.According to an exemplary embodiment, the door server 1700 and thecamera server 1800 are independent servers (e.g., the functionsperformed by one server are not performed by the other server, etc.). Insome embodiments, the door server 1700 and/or the camera server 1800include a plurality of servers. In some embodiments, the door server1700 and the camera server 1800 are a single server or a singleplurality of servers (e.g., the functions of the door server 1700 andthe camera server 1800 described herein may be performed by the sameserver(s), etc.).

As shown in FIG. 11, the electronic door assembly 1100 includes variouselectrically-operated components including a first electrically-operatedcomponent, shown as wireless bridge 1200, a second electrically-operatedcomponent, shown as locking system 1300, a third electrically-operatedcomponent, shown as camera system 1400, and a fourthelectrically-operated component, shown as controller 1500. In someembodiments, the electronic door assembly 1100 does not include one ormore of the wireless bridge 1200, the locking system 1300, the camerasystem 1400, and the controller 1500.

As shown in FIG. 11, the door server 1700 and/or the camera server 1800are configured to communicate with the user devices 1900 (e.g., using afirst communication protocol, using a long-range communication protocol,cellular, Internet, radio, etc.) and the user devices 1900 areconfigured to (i) communicate directly with one or more components ofthe electronic door assembly 1100 (e.g., using a second communicationprotocol, using a short-range communication protocol, Bluetooth,Bluetooth low energy (“BLE”), near-field communication (“NFC”), radiofrequency identification (“RFID”), Wi-Fi, using a long-rangecommunication protocol, cellular, etc.) and/or (ii) communicateindirectly with one or more components of the electronic door assembly1100 (e.g., using a third communication protocol, Wi-Fi, BLE, etc.)through the wireless router 1600 and/or the wireless bridge 1200 (e.g.,when within BLE range, when within range of the wireless router 1600,when within range of the wireless bridge 1200, etc.). The user devices1900 may thereby function as an intermediary device that facilitatesdata transmissions between (i) the door server 1700 and/or the cameraserver 1800 and (ii) one or more components of the electronic doorassembly 1100 (e.g., one or more components of the electronic doorassembly 1100 may be “disconnected devices” that do not communicate withthe door server 1700 and/or the camera server 1800, etc.). In someembodiments, the user devices 1900 are configured to communicate withone or more components of the electronic door assembly 1100 through thedoor server 1700, the camera server 1800, the wireless router 1600,and/or the wireless bridge 1200 (e.g., when not within wireless range ofthe electronic door assembly 1100, etc.). In some embodiments, thecamera server 1800 does not communicate directly with the user devices1900. In such embodiments, the camera server 1800 may communicate withthe user devices 1900 through the door server 1700 (e.g., the doorserver 1700 functions as an intermediary, etc.).

As shown in FIG. 11, the door server 1700 and/or the camera server 1800are configured to communicate with the wireless router 1600 (e.g., usinga long-range communication protocol, Internet, etc.) and the wirelessrouter 1600 is configured to (i) communicate directly with one or morecomponents of the electronic door assembly 1100 (e.g., using Wi-Fi,etc.) and/or (ii) communicate indirectly with one or more components ofthe electronic door assembly 1100 through the wireless bridge 1200(e.g., using Wi-Fi, etc.). The wireless router 1600 may thereby functionas an intermediary device that facilitates data transmissions between(i) the door server 1700 and/or the camera server 1800 and (ii) one ormore components of the electronic door assembly 1100.

According to an exemplary embodiment, the door server 1700 is configuredto manage a plurality of access credentials or user profiles for one ormore users that have access to the locking system 1300, the camerasystem 1400, and/or the controller 1500 of the electronic door assembly1100. In general, a user profile may include one or more files thatinclude data related to operation of the locking system 1300, the camerasystem 1400, and/or the controller 1500. For example, the user profilemay contain a user schedule of when an associated locking system 1300may be accessed (unlocked, locked, etc.). The schedule may specify lockaccess permissions, e.g., by day of the week, including starting times(hours, minutes, etc.) and ending times (hours, minutes, etc.) for eachcorresponding permission. For example, a schedule may specify the timespans in which the associated locking system 1300 may be unlocked viathe user device 1900 of the specific user associated with the userprofile. As another example, the schedule may specify time periods inwhich typical interactions are expected to occur, and a level of trustmay be determined based on these time periods. Accordingly, an unlockrequest sent within an expected time period may be more trusted by theassociated locking system 1300 than a request sent at anunexpected/atypical time. In one embodiment, a default user schedule isset (e.g., by the manufacturer, etc.). Additionally, a list of typicaluser schedules may also be provided to allow a user to select from oneof many configuration options. In this manner, a manufacturer mayprovide various recommended operational settings to a user. A user mayalso customize a schedule to tailor the schedule as he or she desires(e.g., an administrator, etc.).

A user profile may further specify a model/serial number of theassociated locking system 1300 and what types of accesses are availablefor that user. For example, such accesses may include: readingsoftware/hardware version information of the associated locking system1300, updating software of the associated locking system 1300, reading ashackle/latch/dead-bolt state of the associated locking system 1300,locking, unlocking, disarming, reading/setting a time/clock value,reading a battery level, reading/clearing event related data (e.g.,flags, counters, etc.), reading a log of the lock,reading/setting/resetting a keypad code of the associated locking system1300, reading communications data for the associated locking system 1300(e.g., transmission statuses, transmission power levels, channelinformation, addressing information, etc.), reading/setting defaultvalues stored for the associated locking system 1300 (e.g., defaultdisarm times, default unlock times, etc.), among others. A user profilemay also specify a start time and a revocation date/time for the userprofile (i.e., when the user profile begins to be valid and when theuser profile expires and is no longer valid). A user profile may providemaximum disarm/unlock times for the associated locking system 1300. Auser profile may also provide an indication of a trust level of acorresponding user device 1900 (e.g., whether a time value/timestampprovided by the user device 1900 is trusted or not). The locking system1300 may be configured to allow or disallow certain functionality basedon the trust level of a respective user device 1900 requesting accessthereto. The trust level may be stored as an independent permission thatthe user may or may not have access to (e.g., the trust level may bemanaged/adjusted by the software of the locking system 1300, the userdevice 1900, the door server 1700, etc.). As an example, only a highlytrusted user device 1900 may be able to upgrade the firmware of arespective locking system 1300 or change certain settings.

Additionally, the locking system 1300 may have a security algorithm thatfactors in a trust level and time value. For example, as a respectiveuser device 1900 successfully interacts with a respective locking system1300 more often, the respective locking system 1300 may increase (oradjust) a trust level for the respective user device 1900. However, if atime value is out of sync with the maintained time of the respectivelocking system 1300 or authentication fails, the respective lockingsystem 1300 may decrease (or adjust) a trust level for the respectiveuser device 1900. The time value provided by the respective user device1900 may be compared to a time value maintained by the respectivelocking system 1300, and a degree of closeness between the two times maybe used to indicate a trust level for the respective user device 1900(e.g., the closer the two times are to being in sync, the higher thetrust level, etc.). If a trust level decreases below a certainthreshold, the respective locking system 1300 may discontinue or limitinteractions with the respective user device 1900. A trust level mayalso be based on the schedule discussed above. For example, a respectiveuser device 1900 may be regarded as more or less trusted based on thetime the respective user device 1900 is accessing a respective lockingsystem 1300, and whether that time falls within certain time periods asdefined by the schedule. The time value provided by the respective userdevice 1900 may also be used to sync the clock of a respective lockingsystem 1300 with that of the respective user device 1900 or may be usedotherwise during authenticated communications. Any of the user profileitems discussed may have default values (e.g., manufacturer defaults) oruser provided values (e.g., from a user with administrator permissionaccess, etc.). A user profile is not limited to the above data, andadditional data may be included or excluded.

According to an exemplary embodiment, the electronic door system 1000implements an approach that provides for secure communication betweenthe user device 1900 and the locking system 1300 using a two keyauthentication scheme, without both keys being stored on the lockingsystem 1300 (e.g., during a manufacturing phase). In such an embodiment,(i) a first key or a device key is known/stored on the locking system1300 and the door server 1700 that is unique to the locking system 1300and (ii) a second key or a user key is known/stored on each of the userdevices 1900 that is unique to each of the user devices 1900 or userprofiles and not pre-stored on the locking system 1300. Each device key,each user key, and each user profile may be specific to a respectivelocking system 1300. In this manner, the device key, the user key, andthe user profile may uniquely relate to a single locking system 1300.According to an exemplary embodiment, the door server 1700 is configuredto encrypt each user profile with the device key of the locking system1300 that the user profile is associated with. When attempting to accessa locking system 1300, a user device 1900 may receive a deviceidentifier from the locking system 1300 and compare the deviceidentifier to a list of device identifiers associated with one or moreencrypted user profiles currently loaded onto the user device 1900(e.g., that were delivered according to a profile delivery protocol,etc.). If a match is found, the user device 1900 may transmit theassociated encrypted user profile to the locking system 1300. Theencrypted user profile includes the user key. The locking system 1300may decrypt the encrypted user profile using the device key pre-storedthereon to obtain the user key. The user device 1900 may then generateand transmit an encrypted command to the locking system 1300. Theencrypted command is encrypted using the user key. The locking system1300 may then decrypt the encrypted command using the user key obtainedfrom the decrypted user profile and initiate the action specified by thedecrypted command (e.g., unlocking a physical locking component,implementing a firmware update, etc.). In some embodiments, the two keyauthentication process including the device key and the user keyadditionally includes a handshake nonce, a reply nonce, and/or amodified reply nonce, as described in more detail herein.

It should be understood that the two key authentication scheme describedherein between the door server 1700, the user devices 1900, and thelocking systems 1300 may similarly be applied between (i) the doorserver 1700, the user devices 1900, and the controller 1500, (ii) thedoor server 1700, the user devices 1900, and the camera system 1400,and/or (iii) the camera server 1800, the user devices 1900, and thecamera system 1400.

Further, it should be understood that the two key authentication schemedescribed herein is not meant to be limiting, but is provided as anexample of one possible way to provide secure communication between thedoor server 1700, the user devices 1900, and the locking systems 1300 ofthe electronic door system 1000. In other embodiments, securecommunication is otherwise established using a different authenticationscheme such as an authentication scheme that employs digital signatures,challenge-response procedures, multi-factor authentication (e.g.,two-factor authentication, user profile plus a biometric, a user profileplus a PIN, etc.), and/or still other suitable authentication schemes.Further, such a two-key authentication scheme may or may not be used inimplementations where a component of the electronic door assembly 1100is in direct communication with the door server 1700 and/or the cameraserver 1800 (i.e., the communication is routed through the wirelessrouter 1600, not the user devices 1900).

Electronic Door Assembly

As shown in FIGS. 12 and 13, the electronic door assembly 1100 includesa door, shown as door 1102, having a slab (e.g., a solid slab, acomposite slab, etc.), shown as door slab 1104; a jamb, shown as doorjamb 1106; a knob, shown as door knob 1108, configured to facilitateopening the door 1102; and one or more hinges, shown as hinges 1110,pivotally coupling a hinged edge of the door slab 1104 to the door jamb1106. According to the exemplary embodiment shown in FIGS. 12 and 13,one of the hinges 1110 is an electric transfer hinge that facilitatesconnecting one or more electrically-operated door components of theelectronic door assembly 1100 (e.g., the wireless bridge 1200, thelocking system 1300, the camera system 1400, the controller 1500, etc.)to the external power source 1602. In other embodiments, all of thehinges 1110 are standard mechanical hinges and the electrically-operateddoor components are otherwise coupled to the external power source 1602(e.g., via an electrical conduit, etc.).

As shown in FIGS. 12 and 13, the door 1102 includes a first transparentpanel, shown as window 1112, embedded within the door slab 1104. Thewindow 1112 includes a privacy element, shown as blocker 1114, embeddedtherein or integrated therewith. In some embodiments, the blocker 1114is or includes electrically-controllable shades/blinds disposed withinthe window 1112 or disposed along an interior side of the window 1112.In some embodiments, the blocker 1114 is additionally or alternativelyintegrated into or disposed along the window 1112 such that the window1112 has an electrically-controllable opacity (e.g., anelectrically-controllable coating, an electrically-controllable film,etc.). In some embodiments, the door 1102 does not include the window1112 or the window 1112 does not include the blocker 1114.

As shown in FIGS. 12 and 13, the door 1102 includes side panels, shownas panels 1116, disposed along the right side and the left side of thedoor jamb 1106. In other embodiments, the door 1102 includes only one ofthe panels 1116 along the right side of the door jamb 1106 or the leftside of the door jamb 1106. In still other embodiments, the door 1102does not include the panels 1116. As shown in FIGS. 12 and 13, each ofthe panels 1116 includes a second transparent panel, shown as window1118, embedded within the panels 1116. The windows 1118 include privacyelements, shown as blockers 1120, embedded therein or integratedtherewith. In some embodiments, the blockers 1120 are or includeelectrically-controllable shades/blinds disposed within the windows 1118or disposed along an interior side of the windows 1118. In someembodiments, the blockers 1120 are additionally or alternativelyintegrated into or disposed along the windows 1118 such that the windows1118 have an electrically-controllable opacity (e.g., anelectrically-controllable coating, an electrically-controllable film,etc.). In some embodiments, the blockers 1120 are the same as theblocker 1114. In some embodiments, the blockers 1120 are different thanthe blocker 1114. In some embodiments, the panels 1116 do not includethe windows 1118 or the windows 1118 do not include the blockers 1120.

As shown in FIGS. 12 and 13, the electronic door assembly 1100 includesa light source, shown as lighting system 1122, including one or morelighting elements, shown as lights 1124. In some embodiments, the lights1124 are separate from the door 1102 and configured to be disposed alongan exterior surface of a building proximate the door 1102. In someembodiments, the lights 1124 are integrated into the door 1102 (e.g.,the door slab 1104, the door jamb 1106, the panels 1116, etc.). In someembodiments, the lights 1124 are selectively/releasably coupled to thedoor 1102 (e.g., the door 1102 includes one or more light sockets thatmay be selectively accessed, etc.). In some embodiments, the electronicdoor assembly 1100 does not include the lighting system 1122.

As shown in FIGS. 12 and 13, one or more of the wireless bridge 1200,the locking system 1300, the camera system 1400, and the controller 1500are integrated into the door 1102. In some embodiments, one or more ofthe wireless bridge 1200, the locking system 1300, the camera system1400, and the controller 1500 are integrated into the door 1102 at thetime of manufacture. In other embodiments, one or more of the wirelessbridge 1200, the locking system 1300, the camera system 1400, and thecontroller 1500 are integrated into the door 1102 post-manufacture(e.g., by a retailer, by a contractor, by the end consumer, etc.). Insome embodiments, one or more of the wireless bridge 1200, the lockingsystem 1300, the camera system 1400, and the controller 1500 areseparate from the door 1102 or coupled to an exterior thereof.

According to an exemplary embodiment, the electronic door assembly 1100is a modular door assembly. As shown in FIGS. 12 and 13, the door slab1104 includes a first selectively-accessible connection box, shown aslocking system connection box 1130, embedded in the door slab 1104. Inother embodiments, the locking system connection box 1130 is embedded inthe door jamb 1106 and/or the panels 1116. In some embodiments, thelocking system connection box 1130 includes a door or cover thatfacilitates selectively accessing an interior of the locking systemconnection box 1130. As shown in FIGS. 12 and 13, the locking systemconnection box 1130 includes a first interface (e.g., an electricalconnector, etc.), shown as locking system interface 1132, disposedwithin the interior of the locking system connection box 1130 andconfigured to selectively interface with a first connector of thelocking system 1300. Accordingly, the door 1102 can be manufactured andsold without the locking system 1300 and then the end user can selectand install a locking system of their choosing (whetherelectrically-operated or mechanically-operated). In other embodiments,the locking system 1300 is provided with and/or hardwired into the door1102.

As shown in FIGS. 12 and 13, the door slab 1104 includes a secondselectively-accessible connection box, shown as camera system connectionbox 1140, embedded in the door slab 1104. In other embodiments, thecamera system connection box 1140 is embedded in the door jamb 1106and/or the panels 1116. In some embodiments, the camera systemconnection box 1140 includes a door or cover that facilitatesselectively accessing an interior of the camera system connection box1140. As shown in FIGS. 12 and 13, the camera system connection box 1140is configured to selectively receive and hold the camera system 1400. Insome embodiments, the door or cover of the camera system connection box1140 is replaced with a door or cover that defines an aperture when thecamera system 1400 is installed in the door 1102 (e.g., such that acamera lens of the camera system 1400 can see outside of the camerasystem connection box 1140, etc.). As shown in FIGS. 12 and 13, thecamera system connection box 1140 includes a second interface (e.g., anelectrical connector, etc.), shown as camera system interface 1142,disposed within the interior of the camera system connection box 1140and configured to selectively interface with a second connector of thecamera system 1400. Accordingly, the door 1102 can be manufactured andsold without the camera system 1400 and then the end user can select andinstall a camera system of their choosing. In other embodiments, thecamera system 1400 is provided with and/or hardwired into the door 1102.

As shown in FIGS. 12 and 13, the door slab 1104 includes a thirdselectively-accessible connection box, shown as hinge connection box1150, embedded in the door slab 1104. In some embodiments, the hingeconnection box 1150 includes a door or cover that facilitatesselectively accessing an interior of the hinge connection box 1150. Asshown in FIGS. 12 and 13, the hinge connection box 1150 includes a thirdinterface (e.g., an electrical connector, etc.), shown as hingeinterface 1152, disposed within the interior of the hinge connection box1150 and configured to selectively interface with a third connector ofone of the hinges 1110. Accordingly, the door 1102 can be manufacturedand sold without an electric transfer hinge and then the end user canselect and install an electric transfer hinge as desired. In otherembodiments, one of the hinges 1110 is an electric transfer hinge and isprovided with and/or hardwired into the door 1102.

As shown in FIGS. 12 and 13, the locking system connection box 1130 andthe camera system connection box 1140 are electrically coupled to thehinge connection box 1150 (e.g., hardwired, connected duringmanufacturing, etc.) and the hinge 1110 is configured to be electricallyconnected to the external power source 1602. The hinge 1110 maytherefore facilitate powering the locking system 1300 and the camerasystem 1400 with the external power source 1602. As shown in FIGS. 12and 13, the window 1112 is electrically connected to the hingeconnection box 1150. In other embodiments, the window 1112 iselectrically connected directly to the hinge 1110. The hinge 1110 maytherefore facilitate powering the blocker 1114 of the window 1112 withthe external power source 1602. As shown in FIGS. 12 and 13, the windows1118 are electrically connected directly to the hinge 1110. In otherembodiments, the windows 1118 are electrically connected to the hingeconnection box 1150. The hinge 1110 may therefore facilitate poweringthe blockers 1120 of the window 1118 with the external power source1602. As shown in FIGS. 12 and 13, the lighting system 1122 iselectrically connected directly to the hinge 1110. In other embodiments,the lighting system 1122 is electrically connected to the hingeconnection box 1150. The hinge 1110 may therefore facilitate poweringthe lighting system 1122 with the external power source 1602. In stillother embodiments, the lighting system 1122 is directly connected to theexternal power source 1602.

As shown in FIG. 12, the wireless bridge 1200 is separate from the door1102 and connected to the external power source 1602 (e.g., a walloutlet proximate the door 1102, etc.). As shown in FIG. 13, the wirelessbridge 1200 is disposed within the door 1102 and connected to theexternal power source 1602 through the hinge connection box 1150 and/orthe hinge 1110. As shown in FIG. 13, the door slab 1104 includes afourth selectively-accessible connection box, shown as wireless bridgeconnection box 1160, embedded in the door slab 1104 and connected to thehinge connection box 1150. In other embodiments, the wireless bridgeconnection box 1160 is embedded in the door jamb 1106 and/or the panels1116. In some embodiments, the wireless bridge connection box 1160includes a door or cover that facilitates selectively accessing aninterior of the wireless bridge connection box 1160. As shown in FIG.13, the wireless bridge connection box 1160 is configured to selectivelyreceive and hold the wireless bridge 1200. The wireless bridgeconnection box 1160 includes a fourth interface (e.g., an electricalconnector, etc.), shown as wireless bridge interface 1162, disposedwithin the interior of the wireless bridge connection box 1160 andconfigured to selectively interface with a fourth connector of thewireless bridge 1200. Accordingly, the door 1102 can be manufactured andsold without the wireless bridge 1200 and then the end user can selectand install a wireless bridge of their choosing. In other embodiments,the wireless bridge 1200 is provided with and/or hardwired into the door1102. In still other embodiments, the electronic door assembly 1100 doesnot include the wireless bridge 1200. In such embodiments, the lockingsystem 1300, the camera system 1400, and/or the controller 1500 may havethe functionality of the wireless bridge 1200, as described in moredetail herein.

As shown in FIG. 12, the controller 1500 is separate from the door 1102and connected to the blocker 1114, the blockers 1120, and the lightingsystem 1122 to facilitate controlling the operation thereof with thecontroller 1500. According to the exemplary embodiment shown in FIG. 12,the controller 1500 is coupled to the external power source 1602 via thehinge 1110 and/or the hinge connection box 1150. In other embodiments,the controller 1500 is directly coupled to the external power source1602. In some embodiments, the controller 1500 is additionally oralternatively connected to the locking system 1300 and/or the camerasystem 1400 to facilitate controlling the operation thereof with thecontroller 1500.

As shown in FIG. 13, the controller 1500 is disposed within the door1102 and connected to the external power source 1602 through the hingeconnection box 1150 and/or the hinge 1110. As shown in FIG. 13, the doorslab 1104 includes a fifth selectively-accessible connection box, shownas controller connection box 1170, embedded in the door slab 1104 andconnected to the hinge connection box 1150. In other embodiments, thecontroller connection box 1170 is embedded in the door jamb 1106 and/orthe panels 1116. In some embodiments, the controller connection box 1170includes a door or cover that facilitates selectively accessing aninterior of the controller connection box 1170. As shown in FIG. 13, thecontroller connection box 1170 is configured to selectively receive andhold the controller 1500. The controller connection box 1170 includes afifth interface (e.g., an electrical connector, etc.), shown ascontroller interface 1172, disposed within the interior of thecontroller connection box 1170 and configured to selectively interfacewith a fifth connector of the controller 1500. Accordingly, the door1102 can be manufactured and sold without the controller 1500 and thenthe end user can select and install a controller 1500 at the time oftheir choosing. In other embodiments, the controller 1500 is providedwith and/or hardwired into the door 1102. In still other embodiments,the electronic door assembly 1100 does not include the controller 1500.In such embodiments, the locking system 1300 and/or the camera system1400 may have the functionality of the controller 1500.

As shown in FIGS. 12 and 13, the controller 1500 is connected to a userinterface, shown as switch 1606. According to an exemplary embodiment,the switch 1606 is configured to facilitate selectively activating theblocker 1114, the blockers 1120, and/or the lighting system 1122. Insome embodiments, the switch 1606 is configured to be installed in awall proximate the door 1102. In some embodiments, the switch 1606 isconfigured to be installed along the door slab 1104 and/or the panels1116 (e.g., along an interior surface thereof, etc.). In someembodiments, the switch 1606 is wirelessly connected to the controller1500. In some embodiments, the switch 1606 is connected to thecontroller 1500 via a wired connection. In some embodiments, thecontroller 1500 is embedded within the switch 1606.

As shown in FIGS. 12 and 13, the door 1102 includes a secondary powersource, shown as internal energy storage 1604, disposed within the doorslab 1104. In some embodiments, the internal energy storage 1604 isadditionally or alternatively disposed within the door jamb 1106 and/orthe panels 1116. In some embodiments, the internal energy storage 1604is removable. According to an exemplary embodiment, the internal energystorage 1604 is configured to provide power to one or more components ofthe door 1102 (e.g., the wireless bridge 1200, the locking system 1300,the camera system 1400, the controller 1500, the lighting system 1122,etc.) in the event that the external power source 1602 stops poweringthe components of the electronic door assembly 1100 (e.g., in the eventof a power outage, etc.). In some embodiments, the door 1102 does notinclude the internal energy storage 1604.

In some embodiments, the electronic door assembly 1100 is voiceactivation capable. The electronic door assembly 1100 may be configuredto accept various voice commands to the control the locking system 1300,the camera system 1400, the window 1112, the windows 1118, and/or thelighting system 1122. By way of example, the voice commands may includea command to lock or unlock a locking mechanism of the locking system1300. By way of another example, the voice command may include a commandto activate or deactivate a camera device of the camera system 1400. Byway of yet another example, the voice command may include a command toactivate or deactivate the window 1112 and/or the windows 1118. By wayof still another example, the voice command may include a command toturn on or turn off the lights 1124 of the lighting system 1122.

In one implementation, the electronic door assembly 1100 may include amicrophone within the door 1102, the locking system 1300, the camerasystem 1400, and/or the controller 1500. For example, the microphone ofthe electronic door assembly 1100 may be configured to acquire sounddata indicative of a voice command. A component of the electronic doorassembly 1100 (e.g., a processing circuit of the locking system 1300,the camera system 1400, the controller 1500, etc.) may be configured toanalyze the sound data to determine the voice command. In someimplementations, the component of the electronic door assembly 1100 maybe configured to perform a voice authentication process to determinewhether the person is permitted to provide voice commands to theelectronic door assembly 1100. The component of the electronic doorassembly 1100 may then provide the received voice command to anappropriate component of the electronic door assembly 1100 (e.g., thelocking system 1300, the camera system 1400, the controller 1500, etc.)to take action (e.g., lock, unlock, activate, deactivate, turn on, turnoff, etc.).

In another implementation, the electronic door assembly 1100 may beconnectable to an external device that has a microphone such as (i) asmart hub device or a portable smart device (e.g., a smartphone, asmartwatch, a tablet, etc.) having a digital personal assistant (e.g.,Amazon Alexa, Google Assistant, Microsoft Cortana, etc.) or (ii) theswitch 1606. For example, a microphone of the external device may beconfigured to acquire sound data indicative of a voice command. Theexternal device (e.g., a processing circuit thereof, etc.) may beconfigured to analyze the sound data to determine the voice command. Insome implementations, the external device may be configured to perform avoice authentication process to determine whether the person ispermitted to provide voice commands to the electronic door assembly1100. The external device may then provide the received voice command toan appropriate component of the electronic door assembly 1100 (e.g., thelocking system 1300, the camera system 1400, the controller 1500, etc.)to take action (e.g., lock, unlock, activate, deactivate, turn on, turnoff, etc.). As another example, a microphone of the external device maybe configured to acquire sound data indicative of a voice command andthen the external device may transmit the sound data to a component ofthe electronic door assembly 1100 for further processing as describedabove.

Wireless Bridge

In general, the wireless bridge 1200 is configured to receive a firstwireless signal in a first communication protocol and convert the firstsignal to a second wireless signal in a second communication protocol,and vice versa. As shown in FIG. 14, the wireless bridge 1200 includes aprocessing circuit 1202, a first transceiver 1222, and a secondtransceiver 1224. In some embodiments, the wireless bridge 1200 includesa door connector 1226 configured to interface with the wireless bridgeinterface 1162. In some embodiments, the wireless bridge 1200 includesan outlet connector 1228 (e.g., a wall plug, etc.) configured tointerface directly with the external power source 1602 (e.g., a walloutlet, etc.). In some embodiments, the wireless bridge 1200 does notinclude the door connector 1226 or the outlet connector 1228. In suchembodiments, the wireless bridge 1200 may be hardwired within the door1102.

As shown in FIG. 14, the processing circuit 1202 has a processor 1204and a memory 1206. The processing circuit 1202 may include ageneral-purpose processor, an ASIC, one or more FPGAs, a DSP, circuitscontaining one or more processing components, circuitry for supporting amicroprocessor, a group of processing components, or other suitableelectronic processing components. In some embodiments, the processor1204 is configured to execute computer code stored in the memory 1206 tofacilitate the activities described herein. The memory 1206 may be anyvolatile or non-volatile computer-readable storage medium capable ofstoring data or computer code relating to the activities describedherein. According to an exemplary embodiment, the memory 1206 includescomputer code modules (e.g., executable code, object code, source code,script code, machine code, etc.) configured for execution by theprocessor 1204.

According to an exemplary embodiment, the first transceiver 1222 isconfigured to receive and transmit wireless signals using a firstwireless communication protocol. By way of example, the first wirelesscommunication protocol may be a short-range communication protocol. Inone embodiment, the first transceiver 1222 includes Bluetooth componentsfor establishing a Bluetooth connection with a Bluetooth enabled device(e.g., the user devices 1900, the locking system 1300, the controller1500, etc.). According to an exemplary embodiment, the secondtransceiver 1224 is configured to receive and transmit wireless signalsusing a second wireless communication protocol. By way of example, thesecond wireless communication protocol may be a short-rangecommunication protocol. In one embodiment, the second transceiver 1224includes Wi-Fi components for establishing a Wi-Fi connection with aWi-Fi enabled device (e.g., the user devices 1900, the locking system1300, the controller 1500, the wireless router 1600, etc.). In anotherembodiment, the first transceiver 1222 and/or the second transceiver1224 include different types of components that facilitate a differenttype of short-range wireless communication protocol (e.g.,radiofrequency, RFID, ZigBee, NFC, etc.). In other embodiments, thefirst transceiver 1222 and/or the second transceiver 1224 includecomponents that facilitate a long-range wireless communication protocol(e.g., cellular, etc.)

As shown in FIG. 14, the memory 1206 of the wireless bridge 1200includes a bridge circuit 1208. The bridge circuit 1208 may beconfigured to convert a first wireless signal received by the firsttransceiver 1222 in a first wireless communication protocol (e.g., BLE,cellular, etc.) to a second wireless signal in a second communicationprotocol (e.g., Wi-Fi, BLE, etc.) to be emitted by the secondtransceiver 1224. The bridge circuit 1208 may be also configured toconvert the second wireless signal received by the second transceiver1224 in the second wireless communication protocol to the first wirelesssignal in the first communication protocol to be emitted by the firsttransceiver 1222.

As shown in FIG. 14, the bridge circuit 1208 includes a device circuit1210, a profile management circuit 1212, and a communication circuit1214. The device circuit 1210 is configured to acquire a deviceidentifier from devices proximate the wireless bridge 1200 (e.g., basedon an identifier broadcasted by a respective locking system 1300, arespective controller 1500, a respective camera system 1400, etc.). Theprofile management circuit 1212 is configured to receive and storeencrypted bridge profiles and bridge keys sent to the wireless bridge1200 by the door server 1700, as described in more detail herein.

The communication circuit 1214 is configured to generate and transmit anencrypted command to a respective component of a respective electronicdoor assembly 1100. The encrypted command may include a command for therespective locking system 1300, the respective camera system 1400,and/or the respective controller 1500 to initiate a communicationsession with the wireless bridge 1200. According to an exemplaryembodiment, the command is encrypted using the bridge key associatedwith the bridge profile that was transmitted to a component of therespective electronic door assembly 1100 at the start of thecommunication session. In some embodiments, the communication circuit1214 is configured to generate a modified reply nonce based on a replynonce received from the component of the respective electronic doorassembly 1100 as described in more detail herein (e.g., in response tothe component of the respective electronic door assembly 1100successfully decrypting the encrypted bridge profile, etc.). In suchembodiments, the communication circuit 1214 is configured to encrypt thecommand using both the bridge key and the modified reply nonce.

Locking System

In general, the locking system 1300 is configured to receive anencrypted user profile from a respective user device 1900 or the doorserver 1700 (e.g., directly, indirectly through the wireless bridge1200, indirectly through the wireless router 1600, etc.) and make anaccess and/or a management control decision based on the encrypted userprofile (e.g., whether to permit unlocking, updating, etc. by therespective user device 1900). In some embodiments, the locking system1300 is or includes an electronic door lock such as an electricallyoperated deadbolt. In some embodiments, the locking system 1300 is orincludes an electric strike. In some embodiments, the locking system1300 is or includes a magnetically operated locking mechanism (e.g., anelectromagnetic locking mechanism, etc.). In some embodiments, thelocking system 1300 is or includes a mortise locking mechanism. In someembodiments, the locking system 1300 is or includes a multi-pointlockset. In some embodiments, the locking system 1300 includes two ormore of the above in combination. In some embodiments (e.g., embodimentswhere the electronic door assembly 1100 does not include the controller1500, etc.), the functions of the controller 1500 described herein maybe performed by the locking system 1300. In some embodiments, thefunctions of the locking system 1300 described herein may be performedby the controller 1500. In some embodiments, operation of the lockingsystem 1300 is controllable independent of the controller 1500 (e.g.,the controller 1500 and the locking system 1300 perform independentauthentication processes, etc.).

As shown in FIG. 15, the locking system 1300 includes a processingcircuit 1302, a first transceiver 1322, a second transceiver 1324, adoor connector 1326, a user interface 1328, a lock mechanism 1330, and abattery 1332. In some embodiments, the locking system 1300 does notinclude the second transceiver 1324, the door connector 1326, and/or thebattery 1332. The processing circuit 1302 has a processor 1304, a memory1306, and a timer 1320. The processing circuit 1302 may include ageneral-purpose processor, an ASIC, one or more FPGAs, a DSP, circuitscontaining one or more processing components, circuitry for supporting amicroprocessor, a group of processing components, or other suitableelectronic processing components. In some embodiments, the processor1304 is configured to execute computer code stored in the memory 1306 tofacilitate the activities described herein. The memory 1306 may be anyvolatile or non-volatile computer-readable storage medium capable ofstoring data or computer code relating to the activities describedherein. According to an exemplary embodiment, the memory 1306 includescomputer code modules (e.g., executable code, object code, source code,script code, machine code, etc.) configured for execution by theprocessor 1304. The timer 1320 is configured to maintain a time valuefor the locking system 1300. For example, the timer 1320 may be theclock of the processor 1304 or may be any other time keeping circuit ofthe locking system 1300. The time value maintained by the timer 1320 maybe used in secured communications (e.g., in syncing time with the userdevices 1900, in providing timestamps related to events for loggingpurposes, etc.).

According to an exemplary embodiment, the first transceiver 1322 isconfigured to facilitate wireless communication using a firstcommunication protocol. By way of example, the first communicationprotocol may be a short-range communication protocol. In one embodiment,the first transceiver 1322 includes Bluetooth components forestablishing a Bluetooth connection with the user devices 1900, thewireless bridge 1200, the camera system 1400, and/or the controller1500. In another embodiment, the first transceiver 1322 includes adifferent type of components that facilitate a different type ofshort-range and/or wireless communication protocol (e.g.,radiofrequency, RFID, ZigBee, Wi-Fi, NFC, etc.). In embodiments wherethe locking system 1300 includes the second transceiver 1324, the secondtransceiver 1324 is configured to facilitate wireless communicationusing a second communication protocol. In one embodiment, the secondtransceiver 1324 includes wired or wireless (e.g., Wi-Fi) components forcommunicating with Internet connected devices (e.g., the camera system1400, the controller 1500, the wireless router 1600, the user devices1900, the door server 1700, the camera server 1800, etc.). In anotherembodiment, the second transceiver 1324 includes cellular components forcommunicating with the door server 1700, the camera server 1800, and/orthe user devices 1900 via a cellular network.

In embodiments where the locking system 1300 includes the door connector1326, the door connector 1326 is configured to selectively interfacewith the locking system interface 1132. In embodiments where the lockingsystem 1300 does not include the door connector 1326, the locking system1300 may be hardwired within the door 1102.

The user interface 1328 may include a display screen and/or one or moreuser input devices (e.g., touch screens, buttons, microphones, speakers,displays, a keypad, a directional pad, etc.) to allow a user to interactwith the locking system 1300. By way of an example, the user interface1328 may facilitate waking the locking system 1300 from a sleep mode. Byway of another example, the user interface 1328 may facilitate manuallyentering an unlock combination.

The lock mechanism 1330 may include one or more physical and/orelectronic locking mechanisms (e.g., pins, shackles, dials, buttons,shafts, keyholes, motors, latches, deadbolts, etc.). In embodiments thatinclude the battery 1332, the battery 1332 is configured to providepower to the locking system 1300 to facilitate the operation thereof(e.g., locking, unlocking, etc.). The battery 1332 may be rechargeableand/or replaceable. Such a battery operated locking system 1300 maytherefore operate in the event of power loss to the building in whichthe electronic door assembly 1100 is installed. In embodiments that donot include the battery 1332, the locking system 1300 may couple toanother power source to facilitate the operation thereof (e.g., theexternal power source 1602, the internal energy storage 1604, etc.). Insome embodiments, the locking system 1300 includes an input/output port(e.g., a USB port, a COM port, a networking port, etc.) that may be usedto establish a physical connection to another device. For example, sucha physical connection may be used by a manufacturer or installer toprogram or otherwise communicate with the locking system 1300.

According to an exemplary embodiment, the memory 1306 of the lockingsystem 1300 includes various modules or circuits configured to makeaccess control decisions. As shown in FIG. 15, the memory 1306 of thelocking system 1300 includes a user input circuit 1308, an accesscontrol circuit 1310, and a bridge circuit 1312. In some embodiments,the memory 1306 does not include the bridge circuit 1312 (e.g., inembodiments where the electronic door assembly 1100 includes thewireless bridge 1200, in embodiments where the camera system 1400 or thecontroller 1500 function as a wireless bridge, etc.).

The user input circuit 1308 is configured to receive inputs through theuser interface 1328. By way of example, the user input circuit 1308 mayreceive an input to awaken the locking system 1300 from a sleep mode. Byway of another example, the user input circuit 1308 may receive a manualaccess code to unlock or otherwise access the locking system 1300. Byway of another example, the user input circuit 1308 may receive anencrypted user profile and/or an encrypted command from a respectiveuser device 1900 (e.g., directly, indirectly, etc.). By way of yetanother example, the user input circuit 1308 may receive an updated ornew device key from the door server 1700 (e.g., through the user device1900 and/or the wireless bridge 1200, through the wireless router 1600and/or the wireless bridge 1200, etc.).

The access control circuit 1310 is configured to store a deviceidentifier, a device key, and/or a manual access code for the lockingsystem 1300. The access control circuit 1310 may be configured tobroadcast the device identifier via the first transceiver 1322 (e.g., inresponse to being awoken from a sleep mode, etc.). In response to thebroadcast or in response to a user selecting the electronic doorassembly 1100 associated with the locking system 1300 in an app, thelocking system 1300 may receive an associated encrypted user profilefrom a respective user device 1900 or the door server 1700. The accesscontrol circuit 1310 is configured to decrypt the encrypted user profileusing (i) the device key pre-stored thereon and/or (ii) a handshakenonce appended to the encrypted user profile (in embodiments where thehandshake nonce is used) to obtain a user key from the decrypted userprofile. In some embodiments, the access control circuit 1310 isconfigured to generate and transmit a reply nonce to the respective userdevice 1900 or the door server 1700 via the first transceiver 1322 orthe second transceiver 1324 (e.g., depending on the proximity of theuser device 1900 to the locking system 1300, depending on whether thelocking system 1300 only includes the first transceiver 1322, etc.) inresponse to successfully decrypting the encrypted user profile.

The access control circuit 1310 may receive an encrypted command fromthe respective user device 1900 or the door server 1700 (e.g., aftersuccessfully decrypting the encrypted user profile, etc.) via the firsttransceiver 1322 or the second transceiver 1324 (e.g., depending on theproximity of the user device 1900 to the locking system 1300, dependingon whether the locking system 1300 only includes the first transceiver1322, etc.). The access control circuit 1310 is configured to decryptthe encrypted command using the user key obtained from the decrypteduser profile. In some embodiments, the access control circuit 1310 isconfigured to generate a modified reply nonce based on the reply nonceto decrypt the encrypted command along with the user key (in embodimentswhere the access control circuit 1310 generates and transmits the replynonce to the user device 1900 or the door server 1700 and the userdevice 1900 or the door server 1700 generates and encrypts the commandwith the user key and the modified reply nonce). The access controlcircuit 1310 is configured to initiate an action specified by thedecrypted command (e.g., unlocking a physical locking component,implementing a firmware update, etc.) in response to successfullydecrypting the encrypted command. A similar procedure may be performedbetween the wireless bridge 1200 and the access control circuit 1310based on an encrypted bridge profile and encrypted command received fromthe wireless bridge 1200, as described in more detail herein. The accesscontrol circuit 1310 is configured to initiate a communication sessionbetween the locking system 1300 and the wireless bridge 1200 followingsuch a successful procedure.

According to an exemplary embodiment, the access control circuit 1310 isconfigured to perform the decryption of the encrypted user profile andthe encrypted command using a single decryption algorithm. By way ofexample, the decryption algorithm may be or include a Counter withCipher Block Chaining-Message Authentication Code (“CCM”) algorithm asdescribed in further detail in Recommendation for Block Cipher Modes ofOperation: the CCM Mode for Authentication and Confidentiality publishedby the National Institute of Standards and Technology in May 2004 andauthored by Morris Dworkin, which is incorporated herein by reference inits entirety.

In some embodiments, the two key authentication scheme using the devicekey and the user key eliminates any need to pair (e.g., using Bluetoothpairing, etc.) the locking system 1300 to the user devices 1900 tocreate a secure communication session between the locking system 1300and the user devices 1900. In such embodiments, the locking system 1300,therefore, does not store the user keys received from the user devices1900 after a communication session between the locking system 1300 andthe user devices 1900 ends (e.g., after implementing the command, due tothe inability to decrypt the encrypted command, in response to a lack ofreceiving an encrypted command for a predefined period of time, etc.).

It should be understood that the two key authentication schemeimplemented by the access control circuit 1310 described herein is notmeant to be limiting, but is provided as an example of one possible wayto provide secure communication between the user devices 1900 and thelocking system 1300. In other embodiments, secure communication isotherwise established by the access control circuit 1310 using adifferent authentication scheme such as an authentication scheme thatemploys digital signatures, challenge-response procedures, multi-factorauthentication (e.g., two-factor authentication, user profile plus abiometric, a user profile plus a PIN, etc.), and/or still other suitableauthentication schemes. In still other embodiments, the door server 1700performs the access control decision, which is then transmitted to thelocking system 1300 through the user device 1900, through the wirelessbridge 1200/wireless router 1600, or directly. In yet other embodiments,the controller 1500 performs the access control decision, which is thentransmitted to the locking system 1300 directly (e.g., via Bluetooth,through a wired connection, etc.) or indirectly (e.g., through thewireless bridge 1200, through the wireless router 1600, etc.).

The bridge circuit 1312 is configured to convert a first wireless signalreceived by the first transceiver 1322 in the first wirelesscommunication protocol (e.g., BLE, cellular, etc.) to a second wirelesssignal in the second communication protocol (e.g., Wi-Fi, BLE, etc.) tobe emitted by the second transceiver 1324. The bridge circuit 1312 maybe also configured to convert the second wireless signal received by thesecond transceiver 1324 in the second wireless communication protocol tothe first wireless signal in the first communication protocol to beemitted by the first transceiver 1322. Accordingly, the locking system1300 may function as a wireless bridge (e.g., the wireless bridge 1200,etc.).

Camera System

In general, the camera system 1400 is configured to acquire video dataregarding an environment outside the door 1102. The video data may bestored locally and/or remotely in the camera server 1800. As shown inFIG. 16, the camera system 1400 includes a processing circuit 1402, afirst transceiver 1422, a second transceiver 1424, a door connector1426, a camera 1428, a sensor 1430, and a battery 1432. In someembodiments, the camera system 1400 does not include the secondtransceiver 1424, the door connector 1426, the sensor 1430, and/or thebattery 1432. The processing circuit 1402 has a processor 1404, a memory1406, and a timer 1420. The processing circuit 1402 may include ageneral-purpose processor, an ASIC, one or more FPGAs, a DSP, circuitscontaining one or more processing components, circuitry for supporting amicroprocessor, a group of processing components, or other suitableelectronic processing components. In some embodiments, the processor1404 is configured to execute computer code stored in the memory 1406 tofacilitate the activities described herein. The memory 1406 may be anyvolatile or non-volatile computer-readable storage medium capable ofstoring data or computer code relating to the activities describedherein. According to an exemplary embodiment, the memory 1406 includescomputer code modules (e.g., executable code, object code, source code,script code, machine code, etc.) configured for execution by theprocessor 1404. The timer 1420 is configured to maintain a time valuefor the camera system 1400. For example, the timer 1420 may be the clockof the processor 1404 or may be any other time keeping circuit of thecamera system 1400. The time value maintained by the timer 1420 may beused in time stamping the video data acquired by the camera system 1400.

According to an exemplary embodiment, the first transceiver 1422 isconfigured to facilitate wireless communication using a firstcommunication protocol. In one embodiment, the first transceiver 1422includes wired or wireless (e.g., Wi-Fi) components for communicatingwith Internet connected devices (e.g., the controller 1500, the wirelessrouter 1600, the user devices 1900, the door server 1700, the cameraserver 1800, etc.). In another embodiment, the first transceiver 1422includes cellular components for communicating with the door server1700, the camera server 1800, and/or the user devices 1900 via acellular network. In embodiments where the camera system 1400 includesthe second transceiver 1424, the second transceiver 1424 is configuredto facilitate wireless communication using a second communicationprotocol. By way of example, the second communication protocol may be ashort-range communication protocol. In one embodiment, the secondtransceiver 1424 includes Bluetooth components for establishing aBluetooth connection with the user devices 1900, the wireless bridge1200, the camera system 1400, and/or the controller 1500. In anotherembodiment, the second transceiver 1424 includes a different type ofcomponents that facilitate a different type of short-range and/orwireless communication protocol (e.g., radiofrequency, RFID, ZigBee,Wi-Fi, NFC, etc.).

In embodiments where the camera system 1400 includes the door connector1426, the door connector 1426 is configured to selectively interfacewith the camera system interface 1142. In embodiments where the camerasystem 1400 does not include the door connector 1426, the camera system1400 may be hardwired within the door 1102. The camera 1428 is a cameradevice configured to capture the video data. The sensor 1430 may be orinclude a proximity sensor, a motion sensor, a door bell sensor, and/orstill another suitable sensor configured to detect activity outside ofor proximate the door 1102. In embodiments that include the battery1432, the battery 1432 is configured to provide power to the camerasystem 1400 to facilitate the operation thereof (e.g., sense activity,activate the camera 1428, etc.). The battery 1432 may be rechargeableand/or replaceable. Such a battery operated camera system 1400 maytherefore operate in the event of power loss to the building in whichthe electronic door assembly 1100 is installed. In embodiments that donot include the battery 1432, the camera system 1400 may couple toanother power source to facilitate the operation thereof (e.g., theexternal power source 1602, the internal energy storage 1604, etc.).

As shown in FIG. 16, the memory 1406 of the camera system 1400 includesa recording circuit 1408, a sensor circuit 1410, and a bridge circuit1412. In some embodiments, the memory 1406 does not include the sensorcircuit 1410 (e.g., in embodiments where the camera system 1400 does notinclude the sensor 1430, etc.) and/or the bridge circuit 1412 (e.g., inembodiments where the electronic door assembly 1100 includes thewireless bridge 1200, in embodiments where the locking system 1300 orthe controller 1500 function as a wireless bridge, etc.).

The recording circuit 1408 is configured to control operation of thecamera 1428 and control transmission of the video data acquired by thecamera 1428 to the camera server 1800. The recording circuit 1408 maytransmit the video data upon request, periodically according to apreselected or defined transmission interval, or continuously. Thesensor circuit 1410 is configured to receive sensor signals from thesensor 1430 and activate the camera 1428 in response to the sensorsignals indicating activity at or proximate the door 1102. In otherembodiments (e.g., without the sensor 1430, etc.), the camera 1428 maybe continuously active or active during preset time periods.

The bridge circuit 1412 is configured to convert a first wireless signalreceived by the first transceiver 1422 in the first wirelesscommunication protocol (e.g., Wi-Fi, cellular, etc.) to a secondwireless signal in the second communication protocol (e.g., BLE, Wi-Fi,etc.) to be emitted by the second transceiver 1424. The bridge circuit1412 may be also configured to convert the second wireless signalreceived by the second transceiver 1424 in the second wirelesscommunication protocol to the first wireless signal in the firstcommunication protocol to be emitted by the first transceiver 1422.Accordingly, the camera system 1400 may function as a wireless bridge(e.g., the wireless bridge 1200, etc.).

Controller

In general, the controller 1500 is configured to facilitate controllingoperation of one or more components of the electronic door assembly 1100based on a command received thereby. The controller 1500 may receive thecommand from the switch 1606, directly from the user device 1900, and/orindirectly from the user device 1900 through the door server 1700, thewireless router 1600, and/or the wireless bridge 1200. In someembodiments, the controller 1500 is configured to receive an encrypteduser profile from a respective user device 1900 or the door server 1700(e.g., directly, indirectly through the wireless bridge 1200, indirectlythrough the wireless router 1600, etc.) and make an access and/or amanagement control decision based on the encrypted user profile (e.g.,whether to permit unlocking, updating, activation, etc. by therespective user device 1900). In some embodiments (e.g., embodimentswhere the electronic door assembly 1100 does not include the controller1500, etc.), the functions of the controller 1500 described herein maybe performed by the locking system 1300. In some embodiments, thefunctions of the locking system 1300 described herein may be performedby the controller 1500. In some embodiments, operation of the controller1500 is independent of the locking system 1300 (e.g., the controller1500 and the locking system 1300 perform independent authenticationprocesses, etc.).

As shown in FIG. 17, the controller 1500 includes a processing circuit1502, a first transceiver 1522, a second transceiver 1524, a doorconnector 1526, a window interface 1528, a light interface 1530, aswitch interface 1532, and a battery 1534. In some embodiments, thecontroller 1500 does not include the first transceiver 1522, the secondtransceiver 1524, the door connector 1526, the window interface 1528,the light interface 1530, the switch interface 1532, and/or the battery1534. The processing circuit 1502 has a processor 1504, a memory 1506,and a timer 1520. The processing circuit 1502 may include ageneral-purpose processor, an ASIC, one or more FPGAs, a DSP, circuitscontaining one or more processing components, circuitry for supporting amicroprocessor, a group of processing components, or other suitableelectronic processing components. In some embodiments, the processor1504 is configured to execute computer code stored in the memory 1506 tofacilitate the activities described herein. The memory 1506 may be anyvolatile or non-volatile computer-readable storage medium capable ofstoring data or computer code relating to the activities describedherein. According to an exemplary embodiment, the memory 1506 includescomputer code modules (e.g., executable code, object code, source code,script code, machine code, etc.) configured for execution by theprocessor 1504. The timer 1520 is configured to maintain a time valuefor the controller 1500. For example, the timer 1520 may be the clock ofthe processor 1504 or may be any other time keeping circuit of thecontroller 1500. The time value maintained by the timer 1520 may be usedin secured communications (e.g., in syncing time with the user devices1900, in providing timestamps related to events for logging purposes,etc.).

In embodiments where the controller 1500 includes the first transceiver1522, the first transceiver 1522 is configured to facilitate wirelesscommunication using a first communication protocol. By way of example,the first communication protocol may be a short-range communicationprotocol. In one embodiment, the first transceiver 1522 includesBluetooth components for establishing a Bluetooth connection with theuser devices 1900, the wireless bridge 1200, the camera system 1400,and/or the locking system 1300. In another embodiment, the firsttransceiver 1522 includes a different type of components that facilitatea different type of short-range and/or wireless communication protocol(e.g., radiofrequency, RFID, ZigBee, Wi-Fi, NFC, etc.). In embodimentswhere the controller 1500 includes the second transceiver 1524, thesecond transceiver 1524 is configured to facilitate wirelesscommunication using a second communication protocol. In one embodiment,the second transceiver 1524 includes wired or wireless (e.g., Wi-Fi)components for communicating with Internet connected devices (e.g., thecamera system 1400, the locking system 1300, the wireless router 1600,the user devices 1900, the door server 1700, the camera server 1800,etc.). In another embodiment, the second transceiver 1524 includescellular components for communicating with the door server 1700, thecamera server 1800, and/or the user devices 1900 via a cellular network.

In embodiments where the controller 1500 includes the door connector1526, the door connector 1526 is configured to selectively interfacewith the controller interface 1172. In embodiments where the controller1500 does not include the door connector 1526, the controller 1500 maybe hardwired within the door 1102 or separate from the door 1102. Inembodiments where the controller 1500 includes the window interface 1528(e.g., when the door 1102 includes the window 1112, the windows 1118,etc.), the window interface 1528 is configured to connect the controller1500 to the window 1112 and/or the windows 1118 to facilitate providingcommands to the blocker 1114 and the blockers 1120, respectively. Inembodiments where the controller 1500 includes the light interface 1530(e.g., when the door 1102 includes the lighting system 1122, etc.), thelight interface 1530 is configured to connect the controller 1500 to thelighting system 1122 to facilitate providing commands to the lights1124. In embodiments where the controller 1500 includes the switchinterface 1532 (e.g., when the electronic door assembly 1100 includesthe switch 1606, etc.), the switch interface 1532 is configured toconnect the controller 1500 to the switch 1606 to facilitate usercontrol of the blocker 1114, the blockers 1120, and/or the lights 1124with the switch 1606.

In embodiments where the controller 1500 includes the battery 1534, thebattery 1534 is configured to provide power to the controller 1500 tofacilitate the operation thereof (e.g., receiving commands, providingcommands, etc.). The battery 1534 may be rechargeable and/orreplaceable. Such a battery operated controller 1500 may thereforeoperate in the event of power loss to the building in which theelectronic door assembly 1100 is installed. In embodiments that do notinclude the battery 1534, the controller 1500 may couple to anotherpower source to facilitate the operation thereof (e.g., the externalpower source 1602, the internal energy storage 1604, etc.). In someembodiments, the controller 1500 includes an input/output port (e.g., aUSB port, a COM port, a networking port, etc.) that may be used toestablish a physical connection to another device. For example, such aphysical connection may be used by a manufacturer or installer toprogram or otherwise communicate with the controller 1500.

According to an exemplary embodiment, the memory 1506 of the controller1500 includes various modules or circuits configured to facilitatecontrolling operation of one or more components of the electronic doorassembly 1100. As shown in FIG. 17, the memory 1506 of the controller1500 includes a user input circuit 1508, an access control circuit 1510,and a bridge circuit 1512. In some embodiments, the memory 1506 does notinclude the access control circuit 1510 (e.g., in embodiments where thecontroller 1500 does not perform authentication procedures, etc.) and/orthe bridge circuit 1512 (e.g., in embodiments where the electronic doorassembly 1100 includes the wireless bridge 1200, in embodiments wherethe camera system 1400 or the locking system 1300 function as a wirelessbridge, etc.).

The user input circuit 1508 is configured to receive inputs from theswitch 1606, the user devices 1900 (e.g., directly, indirectly, etc.),the door server 1700, and/or the camera server 1800. By way of example,the user input circuit 1508 may receive an encrypted user profile and/oran encrypted command from a respective user device 1900 or the doorserver 1700 (e.g., directly, indirectly, etc.). By way of anotherexample, the user input circuit 1508 may receive a first input from theswitch 1606 to activate/deactivate the blocker 1114 and/or the blockers1120 and/or receive a second input from the switch 1606 to turn on/turnoff the lights 1124. By way of yet another example, the user inputcircuit 1508 may receive an updated or new device key from the doorserver 1700 (e.g., through the user device 1900 and/or the wirelessbridge 1200, through the wireless router 1600 and/or the wireless bridge1200, etc.).

The access control circuit 1510 is configured to store a deviceidentifier and/or a device key. The access control circuit 1510 may beconfigured to broadcast the device identifier via the first transceiver1522. In response to the broadcast or in response to a user selectingthe electronic door assembly 1100 associated with the controller 1500 inan app, the controller 1500 may receive an associated encrypted userprofile from a respective user device 1900 or the door server 1700. Theaccess control circuit 1510 is configured to decrypt the encrypted userprofile using (i) the device key pre-stored thereon and/or (ii) ahandshake nonce appended to the encrypted user profile (in embodimentswhere the handshake nonce is used) to obtain a user key from thedecrypted user profile. In some embodiments, the access control circuit1510 is configured to generate and transmit a reply nonce to therespective user device 1900 or the door sever 1700 via the firsttransceiver 1522 or the second transceiver 1524 (e.g., depending on theproximity of the user device 1900 to the controller 1500, depending onwhether the controller 1500 only includes the first transceiver 1522,etc.) in response to successfully decrypting the encrypted user profile.

The access control circuit 1510 may receive an encrypted command fromthe respective user device 1900 or the door server 1700 (e.g., aftersuccessfully decrypting the encrypted user profile, etc.) via the firsttransceiver 1522 or the second transceiver 1524 (e.g., depending on theproximity of the user device 1900 to the controller 1500, depending onwhether the controller 1500 only includes the first transceiver 1522,etc.). The access control circuit 1510 is configured to decrypt theencrypted command using the user key obtained from the decrypted userprofile. In some embodiments, the access control circuit 1510 isconfigured to generate a modified reply nonce based on the reply nonceto decrypt the encrypted command along with the user key (in embodimentswhere the access control circuit 1510 generates and transmits the replynonce to the user device 1900 and the user device 1900 generates andencrypts the command with the user key and the modified reply nonce).The access control circuit 1510 is configured to initiate an actionspecified by the decrypted command (e.g., unlocking a physical lockingcomponent, implementing a firmware update, turn on/off lights,activating/deactivating blockers, etc.) in response to successfullydecrypting the encrypted command. A similar procedure may be performedbetween the wireless bridge 1200 and the access control circuit 1510based on an encrypted bridge profile and encrypted command received fromthe wireless bridge 1200, as described in more detail herein. The accesscontrol circuit 1510 is configured to initiate a communication sessionbetween the controller 1500 and the wireless bridge 1200 following sucha successful procedure.

According to an exemplary embodiment, the access control circuit 1510 isconfigured to perform the decryption of the encrypted user profile andthe encrypted command using a single decryption algorithm. By way ofexample, the decryption algorithm may be or include a Counter withCipher Block Chaining-Message Authentication Code (“CCM”) algorithm asdescribed in further detail in Recommendation for Block Cipher Modes ofOperation: the CCM Mode for Authentication and Confidentiality publishedby the National Institute of Standards and Technology in May 2004 andauthored by Morris Dworkin.

In some embodiments, the two key authentication scheme using the devicekey and the user key eliminates any need to pair (e.g., using Bluetoothpairing, etc.) the controller 1500 to the user devices 1900 to create asecure communication session between the controller 1500 and the userdevices 1900. In such embodiments, the controller 1500, therefore, doesnot store the user keys received from the user devices 1900 after acommunication session between the controller 1500 and the user devices1900 ends (e.g., after implementing the command, due to the inability todecrypt the encrypted command, in response to a lack of receiving anencrypted command for a predefined period of time, etc.).

It should be understood that the two key authentication schemeimplemented by the access control circuit 1510 described herein is notmeant to be limiting, but is provided as an example of one possible wayto provide secure communication between the user devices 1900 and thecontroller 1500. In other embodiments, secure communication is otherwiseestablished by the access control circuit 1510 using a differentauthentication scheme such as an authentication scheme that employsdigital signatures, challenge-response procedures, multi-factorauthentication (e.g., two-factor authentication, user profile plus abiometric, a user profile plus a PIN, etc.), and/or still other suitableauthentication schemes. In still other embodiments, the door server 1700performs the control decisions, which is then transmitted to thecontroller 1500 through the user device 1900, through the wirelessbridge 1200/wireless router 1600, or directly. In yet other embodiments,the locking system 1300 performs the control decisions, which are thentransmitted to the controller 1500 directly (e.g., via Bluetooth,through a wired connection, etc.) or indirectly (e.g., through thewireless bridge 1200, through the wireless router 1600, etc.). While theauthentication scheme implemented by the controller 1500 and the lockingsystem 1300 are disclosed herein to be the same, in other embodiments,(i) the controller 1500 and the locking system 1300 implement differentauthentication schemes or (ii) authentication to one of the controller1500 or the locking system 1300 automatically grants access to the other(i.e., both don't have to run independent authentication schemes).

The bridge circuit 1512 is configured to convert a first wireless signalreceived by the first transceiver 1522 in the first wirelesscommunication protocol (e.g., BLE, cellular, etc.) to a second wirelesssignal in the second communication protocol (e.g., Wi-Fi, BLE, etc.) tobe emitted by the second transceiver 1524. The bridge circuit 1512 maybe also configured to convert the second wireless signal received by thesecond transceiver 1524 in the second wireless communication protocol tothe first wireless signal in the first communication protocol to beemitted by the first transceiver 1522. Accordingly, the controller 1500may function as a wireless bridge (e.g., the wireless bridge 1200,etc.).

In some embodiments (e.g., where the controller 1500 is Wi-Fi capable,cellular capable, etc.), the controller 1500 is configured to discoverelectronics coupled to the door 1102 and automatically register thecomponents to the door server 1700. By way of example, the controller1500 may detect that a locking system 1300 is installed in the door 1102(e.g., the door connector 1326 is inserted into the locking systeminterface 1132, etc.). The controller 1500 may then pull data from thelocking system 1300 and transmit that data to the door server 1700,which may subsequently link the locking system 1300 with the userprofiles associated with the respective door 1102. Accordingly, whenuser profiles are transmitted to the user devices 1900 associated withthe respective door 1102 by the door server 1700, the user profiles mayinclude the data necessary to access the locking system 1300 (e.g.,without any user interaction necessary to link the locking system 1300to the door 1102 and/or their user devices 1900, etc.).

Door Server

As shown in FIG. 18, the door server 1700 includes a processing circuit1702 and a network interface 1720. The processing circuit 1702 has aprocessor 1704 and a memory 1706. The processing circuit 1702 mayinclude a general-purpose processor, an application specific integratedcircuit (“ASIC”), one or more field programmable gate arrays (“FPGAs”),a digital-signal-processor (“DSP”), circuits containing one or moreprocessing components, circuitry for supporting a microprocessor, agroup of processing components, or other suitable electronic processingcomponents. In some embodiments, the processor 1704 is configured toexecute computer code stored in the memory 1706 to facilitate theactivities described herein. The memory 1706 may be any volatile ornon-volatile computer-readable storage medium capable of storing data orcomputer code relating to the activities described herein. According toan exemplary embodiment, the memory 1706 includes computer code modules(e.g., executable code, object code, source code, script code, machinecode, etc.) configured for execution by the processor 1704.

According to an exemplary embodiment, the network interface 1720 isconfigured to facilitate wireless communication from and to the doorserver 1700 (i) directly to and from the camera server 1800, (ii)directly to and from the user devices 1900, (iii) directly to and fromat least one of the components of the electronic door assembly 1100,(iv) indirectly to and from at least one of the components of theelectronic door assembly 1100 through the user devices 1900 and/or thewireless bridge 1200, (v) indirectly to and from at least one of thecomponents of the electronic door assembly 1100 through the wirelessrouter 1600 and/or the wireless bridge 1200, and/or (vi) indirectly toand from at least one of the components of the electronic door assembly1100 through the user devices 1900 and/or the wireless router 1600.

According to an exemplary embodiment, the memory 1706 of the door server1700 includes various modules or circuits configured to (i) generate andsecurely store the device keys, the user keys, the bridge keys, the userprofiles, and the bridge profiles and (ii) selectively and/ordynamically deliver encrypted user profiles and/or encrypted bridgeprofiles (e.g., each including an associated user key, bridge key, etc.)to the user devices 1900 and/or the wireless bridges 1200 based on oneor more factors such as, for example, the location of the user devices1900, the permissions of the users (e.g., clearance/authorization level,time schedule, etc.) of the user devices 1900, and/or still otherpossible factors.

As shown in FIG. 18, the memory 1706 of the door server 1700 includes adevice key circuit 1708, a user key circuit 1710, a nonce circuit 1712,a user profile circuit 1714, and a camera circuit 1716. In someembodiments, the memory 1706 does not include the nonce circuit 1712and/or the camera circuit 1716. Further, the type of modules or circuitswithin the memory 1706 may vary depending on the authentication schemeutilized. By way of example, when the two-key authentication protocoldescribed herein is used, the door server 1700 may include the devicekey circuit 1708, the user key circuit 1710, the nonce circuit 1712,and/or the user profile circuit 1714. By way of another example, when adifferent authentication protocol is used, the door server 1700 mayinclude various other types of modules or circuits to perform suchauthentication protocols.

The device key circuit 1708 is configured to generate and securely storethe device keys (e.g., which may be provided to the locking system 1300and/or the controller 1500 at the time of manufacturing, etc.). As anexample, the device key circuit 1708 may correspond to a first databaseof keys and may include the software configured to store and retrievesuch keys from the first database. The device key circuit 1708 may befurther configured to facilitate updating, replacing, or deleting thedevice keys (e.g., if a respective device key on a respective lockingsystem 1300 and/or controller 1500 is compromised, etc.), which may bepropagated to the associated locking system 1300 and/or controller 1500using the methods described herein (e.g., directly, indirectly, etc.).

The user key circuit 1710 is configured to generate and securely storethe user keys (e.g., when a user is registered to a respective lockingsystem 1300, controller 1500, etc.). As an example, the user key circuit1710 may correspond to a second database of keys and may include thesoftware configured to store and retrieve such keys from the seconddatabase. The user key circuit 1710 may be further configured tofacilitate updating, replacing, or deleting the user keys (e.g., if auser's access is revoked, if a user key expires, etc.), which may beupdated in the associated user profile as necessary. While not shown,the door server 1700 may also include a bridge key circuit. The bridgekey circuit may be configured to generate and securely store bridgekeys. As an example, the bridge key circuit may correspond to a thirddatabase of keys and may include the software configured to store andretrieve such keys from the third database.

The nonce circuit 1712 is configured to generate a handshake nonce foreach of the user profiles each time the user profiles are transmitted tothe user devices 1900. In some embodiments, the handshake nonce is notused. In some embodiments, the nonce circuit 1712 is configured togenerate a handshake nonce for each of the bridge profiles each time thebridge profiles are transmitted to the wireless bridges 1200.

The user profile circuit 1714 is configured to generate and securelystore the user profiles. As an example, the user profile circuit 1714may correspond to a fourth database of user profiles and may include thesoftware configured to store and retrieve such user profiles from thefourth database. The user profile circuit 1714 may be further configuredto facilitate updating, replacing, or deleting the user profiles. By wayof example, the user profile circuit 1714 may be configured to generatea user profile for a specific user, locking system 1300, and/orcontroller 1500 when a new user is added to a respective locking system1300, added to a respective controller 1500, in response to a respectiveuser profile expiring, etc. The user profile circuit 1714 is furtherconfigured to encrypt the user profiles prior to or as they are beingtransmitted to the user devices 1900. By way of example, when a userprofile is transmitted to a respective user device 1900, the userprofile circuit 1714 may be configured to (i) insert the associated userkey into or append the associated user key to the user profile, (ii)encrypt the user profile and user key using (a) the device keyassociated with a specific locking system 1300 and/or controller 1500and/or (b) the handshake nonce (in embodiments where the handshake nonceis used) to generate an encrypted user profile, and/or (iii) append (a)the user key and/or (b) the handshake nonce (in embodiments where thehandshake nonce is used) to the encrypted user profile. The user profilecircuit 114 may be further configured to facilitate updating, replacing,or deleting the user profiles (e.g., if a user's access is revoked, if auser key is updated, etc.).

While not shown, the door server 1700 may also include a bridge profilecircuit. The bridge profile circuit is configured to generate andsecurely store the bridge profiles. As an example, the bridge profilecircuit may correspond to a fifth database of bridge profiles and mayinclude the software configured to store and retrieve such bridgeprofiles from the fifth database. The bridge profile circuit may befurther configured to facilitate updating, replacing, or deleting thebridge profiles. The bridge profile circuit is further configured toencrypt the bridge profiles prior to or as they are being transmitted tothe wireless bridges 1200. By way of example, when a bridge profile istransmitted to a respective wireless bridge, the bridge profile circuitmay be configured to (i) insert the associated bridge key into or appendthe associated bridge key to the user profile, (ii) encrypt the bridgeprofile and bridge key using (a) the device key associated with aspecific door component or device (e.g., the locking system 1300, thecamera system 1400, the controller 1500, etc.) and/or (b) the handshakenonce (in embodiments where the handshake nonce is used) to generate anencrypted bridge profile, and/or (iii) append (a) the bridge key and/or(b) the handshake nonce (in embodiments where the handshake nonce isused) to the encrypted bridge profile.

The camera circuit 1716 is configured to access the camera server 1800to facilitate accessing the camera server 1800 with the user devices1900. By way of example, in some implementations, the user devices 1900may not be able to access the camera server 1800 directly. Instead, theuser devices 1900 may request to access the camera server 1800 throughan app stored on the user devices 1900, which will cause a request to besent to the camera circuit 1716, which will subsequently contact thecamera server 1800. If the camera server 1800 approves the accessrequest, the camera circuit 1716 may relay pre-stored video, a livevideo stream, and/or provide other control functionality to the userdevices 1900.

Camera Server

As shown in FIG. 19, the camera server 1800 includes a processingcircuit 1802 and a network interface 1820. The processing circuit 1802has a processor 1804 and a memory 1806. The processing circuit 1802 mayinclude a general-purpose processor, an application specific integratedcircuit (“ASIC”), one or more field programmable gate arrays (“FPGAs”),a digital-signal-processor (“DSP”), circuits containing one or moreprocessing components, circuitry for supporting a microprocessor, agroup of processing components, or other suitable electronic processingcomponents. In some embodiments, the processor 1804 is configured toexecute computer code stored in the memory 1806 to facilitate theactivities described herein. The memory 1806 may be any volatile ornon-volatile computer-readable storage medium capable of storing data orcomputer code relating to the activities described herein. According toan exemplary embodiment, the memory 1806 includes computer code modules(e.g., executable code, object code, source code, script code, machinecode, etc.) configured for execution by the processor 1804.

According to an exemplary embodiment, the network interface 1820 isconfigured to facilitate wireless communication from and to the cameraserver 1800 (i) directly to and from the door server 1700, (ii) directlyto and from the user devices 1900, (iii) directly to and from the camerasystem 1400, (iv) indirectly to and from the user devices 1900, (v)indirectly to and from the camera system 1400 through the user devices1900 and/or the wireless bridge 1200, (vi) indirectly to and from thecamera system 1400 through the wireless router 1600 and/or the wirelessbridge 1200, and/or (vii) indirectly to and from the camera system 1400through the user devices 1900 and/or the wireless router 1600.

According to an exemplary embodiment, the memory 1806 of the cameraserver 1800 includes various modules or circuits configured to receive,store, and transmit video data acquired by the camera system 1400 to theuser devices 1900. As shown in FIG. 19, the memory 1806 of the cameraserver 1800 includes an access circuit 1808 and a camera circuit 1810.The camera circuit 1810 is configured to receive and store video dataacquired by the camera system 1400. The access circuit 1808 isconfigured to determine whether a respective user device 1900 ispermitted to access the camera data stored in the camera circuit 1810.According to an exemplary embodiment, a user is able to link a camerasystem 1400 to their user profile (e.g., at the time of installing thecamera system 1400 in the door 1102, etc.). Accordingly, when the userattempts to access the video data (e.g., through the camera circuit 1716of the door server 1700, etc.), the access circuit 1808 is configured todetermine if the user profile on the user device 1900 attempting toaccess the camera data is associated with the camera system 1400 thatacquired the video data. If so, the access circuit 1808 is configured totransmit the video data to the user device 1900 for viewing (e.g.,directly, through the camera circuit 1716 of the door server 1700,etc.). In some embodiments, the user devices 1900 can access a livevideo feed directly from the camera system 1400 without having to gothrough the camera server 1800. In such embodiments, the camera system1400 may be configured to implement a similar authentication schemedescribed herein in relation to the locking system 1300 and thecontroller 1500.

User Device

In general, the user device 1900 is configured to selectively receiveand store an encrypted user profile from the door server 1700 tofacilitate accessing and/or at least partially managing the operation ofone or more components of the electronic door assembly 1100 to which theuser device 1900 has access. By way of example, the user device 1900 maybe used to unlock, lock, and/or otherwise manage the function of thelocking system 1300 (e.g., change settings, update firmware, etc.directly through the locking system 1300 or indirectly through thecontroller 1500). By way of another example, the user device 1900 may beused to activate, deactivate, and/or otherwise manage the function ofthe lighting system 1122, the window 1112, and/or the windows 1118(e.g., through the controller 1500, through the locking system 1300,etc.). By way of yet another example, the user device 1900 may be usedto (i) activate and deactivate the camera system 1400 and/or (ii) viewlive and/or pre-recorded video captured by the camera system 1400. Theuser device 1900 may access, control, and/or manage various componentsof the electronic door system 1000 through the use of an application(“app”) that is configured to run on the user device 1900. For example,the app may be installed on a mobile phone or other portable device, andthe app may be used to configure, control, and/or communicate with thewireless bridge 1200, the locking system 1300, the camera system 1400,the controller 1500, the wireless router 1600, the door server 1700,and/or the camera server 1800 over a wireless connection. In someembodiments, the user device 1900 is a portable device such as asmartphone, a cell phone, a mobile phone, a tablet, a smart watch, alaptop computer, and/or another type of suitable portable device. Inanother embodiment, the user device 1900 is a desktop computer (e.g.,connected to the electronic door assembly 1100 via a wired connection,remote from the electronic door assembly 1100, etc.).

As shown in FIG. 20, the user device 1900 includes a processing circuit1902, a first transceiver 1922, a second transceiver 1924, a thirdtransceiver 1926, and a user interface 1928. The processing circuit 1902has a processor 1904, a memory 1906, and a timer 1920. The processingcircuit 1902 may include a general-purpose processor, an ASIC, one ormore FPGAs, a DSP, circuits containing one or more processingcomponents, circuitry for supporting a microprocessor, a group ofprocessing components, or other suitable electronic processingcomponents. In some embodiments, the processor 1904 is configured toexecute computer code stored in the memory 1906 to facilitate theactivities described herein. The memory 1906 may be any volatile ornon-volatile computer-readable storage medium capable of storing data orcomputer code relating to the activities described herein. According toan exemplary embodiment, the memory 1906 includes computer code modules(e.g., executable code, object code, source code, script code, machinecode, etc.) configured for execution by the processor 1904. The timer1920 is configured to maintain a time value for the user device 1900.For example, the timer 1920 may be the clock of the processor 1904 ormay be any other time keeping circuit of the user device 1900. The timevalue maintained by the timer 1920 may be used in secured communications(e.g., in syncing time with the locking system 1300, in providingtimestamps related to events for logging purposes, etc.).

According to an exemplary embodiment, (i) the first transceiver 1922 isconfigured to facilitate communicating with one or more of thecomponents of the electronic door system 1000 using a firstcommunication protocol, (ii) the second transceiver 1924 is configuredto facilitate communicating with one or more of the components of theelectronic door system 1000 using a second communication protocol, and(iii) the third transceiver 1926 is configured to facilitatecommunicating with one or more of the components of the electronic doorsystem 1000 using a third communication protocol. By way of example, (i)at least one of the first communication protocol, the secondcommunication protocol, or the third communication protocol may be along-range communication protocol and (ii) at least one of the firstcommunication protocol, the second communication protocol, or the thirdcommunication protocol may be a short-range communication protocol. Inone embodiment, the first transceiver 1922 includes cellular componentsfor communicating with (i) the door server 1700 and/or the camera server1800 via a cellular network and/or (ii) the electronic door assembly1100 through the door server 1700 and/or the camera server 1800. In someembodiments, the cellular components facilitate communicating directlywith components of the electronic door assembly 1100 directly (e.g.,without the door server 1700, the camera server 1800, the wirelessrouter 1600, the wireless bridge 1200, etc. functioning as anintermediary; one or more components of the electronic door assembly1100 include cellular components; etc.). In one embodiment, the secondtransceiver 1924 includes wireless (e.g., Wi-Fi, etc.) components forcommunicating with (i) the door server 1700 and/or the camera server1800 over the Internet or other network, (ii) one or more components ofthe electronic door assembly 1100 directly (e.g., when in Wi-Fi range,etc.), and/or (iii) one or more components of the electronic doorassembly 1100 indirectly through the wireless bridge 1200, wirelessrouter 1600, the door server 1700, and/or the camera server 1800 (e.g.,when connected to an internet connection, etc.). In one embodiment, thethird transceiver 1926 includes Bluetooth components for establishing aBluetooth connection with (i) one or more components of the electronicdoor assembly 1100 directly (e.g., when in range of Bluetooth compatiblecomponents of the electronic door assembly 1100, etc.) and/or (ii) oneor more components of the electronic door assembly 1100 indirectlythrough the wireless bridge 1200 (e.g., when in Bluetooth range of thewireless bridge 1200 and when attempting to communicate withnon-Bluetooth compatible components of the electronic door assembly1100, etc.). In another embodiment, the third transceiver 1926 includesa different type of components that facilitate a different type ofshort-range and/or wireless communication protocol (e.g.,radiofrequency, RFID, ZigBee, NFC, etc.). In some embodiments, the userdevice 1900 does not include one or more of the first transceiver 1922,the second transceiver 1924, and the third transceiver 1926.

The user interface 1928 may include a display screen and/or one or moreuser input devices (e.g., touch screens, buttons, microphones, speakers,displays, keyboards, stylus inputs, mice, track pads, etc.) to allow auser to interact with the user device 1900, the locking system 1300, thecamera system 1400, the controller 1500, the door server 1700, thecamera server 1800, and/or any apps running on the user device 1900.

According to an exemplary embodiment, the memory 1906 of the user device1900 includes various modules or circuits configured to receive, manage,and transmit the encrypted user profiles and/or the encrypted commands.As shown in FIG. 20, the memory 1906 of the user device 1900 includes anapplication circuit 1908 having a profile management circuit 1910, auser input circuit 1912, a door system circuit 1914, and a commandcircuit 1918.

The profile management circuit 1910 is configured to receive and storethe encrypted user profiles and user keys sent to the first transceiver1922 and/or the second transceiver 1924 of the user device 1900 by thedoor server 1700. The user input circuit 1912 is configured to (i)provide various graphical user interfaces on a display of the userinterface 1928 and (ii) receive inputs provided to the user interface1928 by the user and perform functions associated therewith. The doorsystem circuit 1914 is configured to identify a respective electronicdoor assembly 1100 that the user device 1900 is trying to access (e.g.,based on an identifier broadcasted by a respective locking system 1300,a respective controller 1500, etc.; based on an electronic door assembly1100 selected in the app on the user device 1900; etc.) and provide thecorresponding encrypted user profile (e.g., without the appended userkey, with the handshake nonce appended, etc.) stored in the profilemanagement circuit 1910 to the first transceiver 1922, the secondtransceiver 1924, and/or the third transceiver 1926 (depending on thecurrent connections available and the proximity of the user device 1900to the electronic door assembly 1100) to deliver the encrypted userprofile to the respective electronic door assembly 1100 to facilitatecontrolling various functions of the respective electronic door assembly1100 (e.g., unlock, lock, change settings, update firmware, turn onlights, activate blockers, etc.).

The command circuit 1916 is configured to generate and transmit anencrypted command to the respective electronic door assembly 1100. Theencrypted command may include a command for the respective lockingsystem 1300 to perform some action such as unlock, lock, changesettings, update firmware, etc. The encrypted command may include acommand for the respective controller 1500 to perform some action suchas unlock, lock, change settings, update firmware, turn on lights, turnoff lights, activate blockers, deactivate blockers, activate camera,deactivate camera, etc. The encrypted command may include a command forthe respective camera system 1400 to activate, deactivate, provide alive feed, etc. According to an exemplary embodiment, the command isencrypted using the user key associated with the user profile that wastransmitted to a component of the respective electronic door assembly1100 at the start of the communication session. In some embodiments, thecommand circuit 1916 is configured to generate a modified reply noncebased on a reply nonce received from the component of the respectiveelectronic door assembly 1100 as described in more detail herein (e.g.,in response to the component of the respective electronic door assembly1100 successfully decrypting the encrypted user profile, etc.). In suchembodiments, the command circuit 1916 is configured to encrypt thecommand using both the user key and the modified reply nonce.

Communication Processes

Referring now to FIGS. 21-25, various possible communication processesbetween components of the electronic door system 1000 are shownaccording to various exemplary embodiments. As shown in FIG. 21, a firstcommunication process 2100 is shown according to an embodiment where auser device (e.g., the user device 1900, etc.) is within communicationrange (e.g., BLE, Wi-Fi, cellular, etc.) of a door device (e.g., thelocking system 1300, the camera system 1400, the controller 1500, etc.)such that the user device can communicate directly with the door devicevia a short-range communication protocol or a long-range communicationprotocol (e.g., without an intermediary device, etc.). At ACT1, a server(e.g., the door server 1700, etc.) receives a request to add a user orthe user device to a door system (e.g., the door system 1000, etc.)including the door device. At ACT2, the server is configured to generatean encrypted user profile in response to the request. The server isconfigured to encrypt the user profile and a user key with a device keyassociated with the door device and a handshake nonce. The server isconfigured to append the user key associated with the user device andthe handshake nonce to the encrypted user profile. At ACT3, the serveris configured to transmit the encrypted user profile to the user device.

At ACT4, the user device is configured to store the user key appended tothe encrypted user profile. At ACT5, the user device is configured totransmit the encrypted user profile with the handshake nonce appendedthereto to the door device. At ACT6, the door device is configured todecrypt the encrypted user profile with a pre-stored device key and theappended handshake nonce to obtain the user key from the decrypted userprofile. At ACT7, the door device is configured to generate a replynonce. At ACT8, the door device is configured to transmit the replynonce to the user device.

At ACT9, the user device is configured to generate a modified replynonce based on the reply nonce received from the door device. At ACT10,the user device is configured to generate an encrypted command. Thecommand is encrypted using the user key and the modified reply nonce. AtACT11, the user device is configured to transmit the encrypted commandto the door device. At ACT12, the door device is configured to generatea modified reply nonce based on the reply nonce (i.e., independent ofthe user device). At ACT13, the door device is configured to decrypt theencrypted command using the user key obtained from the user profile andthe modified reply nonce. The door device is then configured to performan action specified by the decrypted command. It should be understoodthat, in some implementations, the handshake nonce, the reply nonce, andthe modified reply nonce are omitted from the first communicationprocess 2100.

As shown in FIG. 22, a second communication process 2200 is shownaccording to an embodiment where a user device (e.g., the user device1900, etc.) is not within short-range communication (e.g., BLE, etc.) ofa door device (e.g., the locking system 1300, the camera system 1400,the controller 1500, etc.) but is within short-range communication(e.g., Wi-Fi, etc.) of an intermediary device (e.g., the wireless bridge1200, the wireless router 1600, etc.) such that the user device cancommunicate with the door device via a short-range communicationprotocol through the intermediary device. At ACT1, the door device isconfigured to broadcast a device identifier (e.g., periodically,continuously, when awoken, etc.). At ACT2, a bridge (e.g., the wirelessbridge 1200, etc.) is configured to receive the device identifier andtransmit a request for a bridge profile with the device identifier to aserver (e.g., the door server 1700, etc.) through a router (e.g., thewireless router 1600, etc.).

At ACT3, the server is configured to generate an encrypted bridgeprofile in response to the request and based on the device identifier.The server is configured to encrypt the bridge profile and a bridge keywith a device key associated with the door device and a handshake nonce.The server is configured to append the bridge key associated with thebridge and the handshake nonce to the encrypted bridge profile. At ACT4,the server is configured to transmit the encrypted bridge profile to thebridge through the router.

At ACT5, the bridge is configured to store the bridge key appended tothe encrypted bridge profile. At ACT6, the bridge is configured totransmit the encrypted bridge profile with the handshake nonce appendedthereto to the door device. At ACT7, the door device is configured todecrypt the encrypted bridge profile with a pre-stored device key andthe appended handshake nonce to obtain the bridge key from the decryptedbridge profile. At ACT8, the door device is configured to generate areply nonce. At ACT9, the door device is configured to transmit thereply nonce to the bridge.

At ACT10, the bridge is configured to generate a modified reply noncebased on the reply nonce received from the door device. At ACT11, thebridge is configured to generate an encrypted command. The command isencrypted using the bridge key and the modified reply nonce. At ACT12,the bridge is configured to transmit the encrypted command to the doordevice. At ACT13, the door device is configured to generate a modifiedreply nonce based on the reply nonce (i.e., independent of the bridge).At ACT14, the door device is configured to decrypt the encrypted commandusing the bridge key obtained from the bridge profile and the modifiedreply nonce. The door device is then configured to perform an actionspecified by the decrypted command, in this instance, initiate acommunication session between the bridge and the door device.

At ACT15, the server receives a request to add a user or the user deviceto a door system (e.g., the door system 1000, etc.) including the doordevice. ACT15 can come before, during, or after ACT1-ACT14. At ACT16,the server is configured to generate an encrypted user profile inresponse to the request. The server is configured to encrypt the userprofile and a user key with a device key associated with the door deviceand a handshake nonce. The server is configured to append the user keyassociated with the user device and the handshake nonce to the encrypteduser profile. At ACT17, the server is configured to transmit theencrypted user profile to the user device. In some embodiments, ACT17includes transmitting the encrypted user profile to the user devicethrough the router.

At ACT18, the user device is configured to store the user key appendedto the encrypted user profile. At ACT19, the user device is configuredto transmit the encrypted user profile to the door device through therouter and the bridge. At ACT20, the door device is configured todecrypt the encrypted user profile with the pre-stored device key andthe appended handshake nonce to obtain the user key from the decrypteduser profile. At ACT21, the door device is configured to generate areply nonce. At ACT22, the door device is configured to transmit thereply nonce to the user device through the bridge and the router.

At ACT23, the user device is configured to generate a modified replynonce based on the reply nonce received from the door device. At ACT24,the user device is configured to generate an encrypted command. Thecommand is encrypted using the user key and the modified reply nonce. AtACT25, the user device is configured to transmit the encrypted commandto the door device through the router and the bridge. At ACT26, the doordevice is configured to generate a modified reply nonce based on thereply nonce (i.e., independent of the user device). At ACT27, the doordevice is configured to decrypt the encrypted command using the user keyobtained from the user profile and the modified reply nonce. The doordevice is then configured to perform an action specified by thedecrypted command.

It should be understood that, in some implementations, the handshakenonce, the reply nonce, and the modified reply nonce are omitted fromthe second communication process 2200. In some embodiments, the bridgedoes not perform ACT2 until the user device performs ACT19 (e.g., thebridge requests the bridge profile to establish communication with thedoor device after the user device requests access such that continuouscommunication with the door device is not necessary). In someembodiments, the bridge does not perform ACT6 until the user deviceperforms ACT19 (e.g., the bridge establishes communication with the doordevice after the user device requests access such that continuouscommunication with the door device is not necessary, etc.). In someinstances, ACT19, ACT22, and ACT25 are performed between the userdevice, the bridge, and the door device and not the router (e.g., whenthe user device is in range of the bridge, etc.).

As shown in FIG. 23, a third communication process 2300 is shownaccording to an embodiment where a user device (e.g., the user device1900, etc.) is not within short-range communication (e.g., BLE, Wi-Fi,etc.) of a door device (e.g., the locking system 1300, the camera system1400, the controller 1500, etc.) or an intermediary device (e.g., thewireless bridge 1200, the wireless router 1600, etc.). At ACT1, the doordevice is configured to broadcast a device identifier (e.g.,periodically, continuously, when awoken, etc.). At ACT2, a bridge (e.g.,the wireless bridge 1200, etc.) is configured to receive the deviceidentifier and transmit a request for a bridge profile with the deviceidentifier to a server (e.g., the door server 1700, etc.) through arouter (e.g., the wireless router 1600, etc.).

At ACT3, the server is configured to generate an encrypted bridgeprofile in response to the request and based on the device identifier.The server is configured to encrypt the bridge profile and a bridge keywith a device key associated with the door device and a handshake nonce.The server is configured to append the bridge key associated with thebridge and the handshake nonce to the encrypted bridge profile. At ACT4,the server is configured to transmit the encrypted bridge profile to thebridge through the router.

At ACT5, the bridge is configured to store the bridge key appended tothe encrypted bridge profile. At ACT6, the bridge is configured totransmit the encrypted bridge profile with the handshake nonce appendedthereto to the door device. At ACT7, the door device is configured todecrypt the encrypted bridge profile with a pre-stored device key andthe appended handshake nonce to obtain the bridge key from the decryptedbridge profile. At ACT8, the door device is configured to generate areply nonce. At ACT9, the door device is configured to transmit thereply nonce to the bridge.

At ACT10, the bridge is configured to generate a modified reply noncebased on the reply nonce received from the door device. At ACT11, thebridge is configured to generate an encrypted command. The command isencrypted using the bridge key and the modified reply nonce. At ACT12,the bridge is configured to transmit the encrypted command to the doordevice. At ACT13, the door device is configured to generate a modifiedreply nonce based on the reply nonce (i.e., independent of the bridge).At ACT14, the door device is configured to decrypt the encrypted commandusing the bridge key obtained from the bridge profile and the modifiedreply nonce. The door device is then configured to perform an actionspecified by the decrypted command, in this instance, initiate acommunication session between the bridge and the door device.

At ACT15, the user device is configured to transmit an access request tothe server to access the door device. In some embodiments (e.g., ininstances where the user device 1900 is within short-range communicationof the wireless router 1600, etc.), ACT15 is replaced with ACT15A andACT15B. At ACT15A, the user device is configured to transmit an accessrequest to the router. At ACT15B, the router is configured to transmitthe access request to the server. At ACT16, the server is configured togenerate an encrypted user profile in response to the request. Theserver is configured to encrypt the user profile and a user key with thedevice key associated with the door device and a handshake nonce. Theserver is configured to append the handshake nonce to the encrypted userprofile. At ACT17, the server is configured to transmit the encrypteduser profile to the door device through the router and the bridge.

At ACT18, the door device is configured to decrypt the encrypted userprofile with the pre-stored device key and the appended handshake nonceto obtain the user key from the decrypted user profile. At ACT19, thedoor device is configured to generate a reply nonce. At ACT20, the doordevice is configured to transmit the reply nonce to the server throughthe bridge and the router.

At ACT21, the server is configured to generate a modified reply noncebased on the reply nonce received from the door device. At ACT22, theserver is configured to generate an encrypted command based on theaccess request. The command is encrypted using the user key and themodified reply nonce. At ACT23, the server is configured to transmit theencrypted command to the door device through the router and the bridge.At ACT24, the door device is configured to generate a modified replynonce based on the reply nonce (i.e., independent of the server). AtACT25, the door device is configured to decrypt the encrypted commandusing the user key obtained from the user profile and the modified replynonce. The door device is then configured to perform an action specifiedby the decrypted command.

It should be understood that, in some implementations, the handshakenonce, the reply nonce, and the modified reply nonce are omitted fromthe third communication process 2300. In some embodiments, the bridgedoes not perform ACT2 until the user device performs ACT15 (e.g., thebridge requests the bridge profile to establish communication with thedoor device after the user device requests access such that continuouscommunication with the door device is not necessary). In someembodiments, the bridge does not perform ACT6 until the user deviceperforms ACT15 (e.g., the bridge establishes communication with the doordevice after the user device requests access such that continuouscommunication with the door device is not necessary, etc.).

As shown in FIG. 24, a fourth communication process 2400 is shownaccording to an embodiment where a user device (e.g., the user device1900, etc.) is not within short-range communication (e.g., BLE, Wi-Fi,etc.) of a door device (e.g., the locking system 1300, the camera system1400, the controller 1500, etc.) or an intermediary device (e.g., thewireless bridge 1200, the wireless router 1600, etc.). At ACT1, the userdevice is configured to transmit an access request to the server toaccess the door device. In some embodiments (e.g., in instances wherethe user device 1900 is within short-range communication of the wirelessrouter 1600, etc.), ACT1 is replaced with ACT1A and ACT1B. At ACT1A, theuser device is configured to transmit an access request to the router.At ACT1B, the router is configured to transmit the access request to theserver. At ACT2, the server is configured to generate an encrypted userprofile in response to the request. The server is configured to encryptthe user profile and a user key with the device key associated with thedoor device and a handshake nonce. The server is configured to appendthe handshake nonce to the encrypted user profile. At ACT3, the serveris configured to transmit the encrypted user profile to the door devicethrough the router and the bridge.

At ACT4, the door device is configured to decrypt the encrypted userprofile with the pre-stored device key and the appended handshake nonceto obtain the user key from the decrypted user profile. At ACT5, thedoor device is configured to generate a reply nonce. At ACT6, the doordevice is configured to transmit the reply nonce to the server throughthe bridge and the router.

At ACT7, the server is configured to generate a modified reply noncebased on the reply nonce received from the door device. At ACT8, theserver is configured to generate an encrypted command based on theaccess request. The command is encrypted using the user key and themodified reply nonce. At ACT9, the server is configured to transmit theencrypted command to the door device through the router and the bridge.At ACT10, the door device is configured to generate a modified replynonce based on the reply nonce (i.e., independent of the server). AtACT11, the door device is configured to decrypt the encrypted commandusing the user key obtained from the user profile and the modified replynonce. The door device is then configured to perform an action specifiedby the decrypted command. It should be understood that, in someimplementations, the handshake nonce, the reply nonce, and the modifiedreply nonce are omitted from the fourth communication process 2400.

As shown in FIG. 25, a fifth communication process 2500 is shownaccording to an embodiment where a user device (e.g., the user device1900, etc.) is not within short-range communication (e.g., BLE, Wi-Fi,etc.) of a door device (e.g., the locking system 1300, the camera system1400, the controller 1500, etc.) or an intermediary device (e.g., thewireless bridge 1200, the wireless router 1600, etc.). At ACT1, a server(e.g., the door server 1700, etc.) receives a request to add a user orthe user device to a door system (e.g., the door system 1000, etc.)including the door device. At ACT2, the server is configured to generatean encrypted user profile in response to the request. The server isconfigured to encrypt the user profile and a user key with a device keyassociated with the door device and a handshake nonce. The server isconfigured to append the user key associated with the user device andthe handshake nonce to the encrypted user profile. At ACT3, the serveris configured to transmit the encrypted user profile to the user device.

At ACT4, the user device is configured to store the user key appended tothe encrypted user profile. At ACT5, the user device is configured totransmit the encrypted user profile with the handshake nonce appendedthereto to the door device through the server, the router, and thebridge. At ACT6, the door device is configured to decrypt the encrypteduser profile with a pre-stored device key and the appended handshakenonce to obtain the user key from the decrypted user profile. At ACT7,the door device is configured to generate a reply nonce. At ACT8, thedoor device is configured to transmit the reply nonce to the user devicethrough the bridge, the router, and the server.

At ACT9, the user device is configured to generate a modified replynonce based on the reply nonce received from the door device. At ACT10,the user device is configured to generate an encrypted command. Thecommand is encrypted using the user key and the modified reply nonce. AtACT11, the user device is configured to transmit the encrypted commandto the door device through the server, the router, and the bridge. AtACT12, the door device is configured to generate a modified reply noncebased on the reply nonce (i.e., independent of the user device). AtACT13, the door device is configured to decrypt the encrypted commandusing the user key obtained from the user profile and the modified replynonce. The door device is then configured to perform an action specifiedby the decrypted command. It should be understood that, in someimplementations, the handshake nonce, the reply nonce, and the modifiedreply nonce are omitted from the fifth communication process 2500.

As utilized herein, the terms “approximately,” “about,” “substantially”,and similar terms are intended to have a broad meaning in harmony withthe common and accepted usage by those of ordinary skill in the art towhich the subject matter of this disclosure pertains. It should beunderstood by those of skill in the art who review this disclosure thatthese terms are intended to allow a description of certain featuresdescribed and claimed without restricting the scope of these features tothe precise numerical ranges provided. Accordingly, these terms shouldbe interpreted as indicating that insubstantial or inconsequentialmodifications or alterations of the subject matter described and claimedare considered to be within the scope of the disclosure as recited inthe appended claims.

It should be noted that the term “exemplary” and variations thereof, asused herein to describe various embodiments, are intended to indicatethat such embodiments are possible examples, representations, orillustrations of possible embodiments (and such terms are not intendedto connote that such embodiments are necessarily extraordinary orsuperlative examples).

The term “coupled” and variations thereof, as used herein, means thejoining of two members directly or indirectly to one another. Suchjoining may be stationary (e.g., permanent or fixed) or moveable (e.g.,removable or releasable). Such joining may be achieved with the twomembers coupled directly to each other, with the two members coupled toeach other using a separate intervening member and any additionalintermediate members coupled with one another, or with the two memberscoupled to each other using an intervening member that is integrallyformed as a single unitary body with one of the two members. If“coupled” or variations thereof are modified by an additional term(e.g., directly coupled), the generic definition of “coupled” providedabove is modified by the plain language meaning of the additional term(e.g., “directly coupled” means the joining of two members without anyseparate intervening member), resulting in a narrower definition thanthe generic definition of “coupled” provided above. Such coupling may bemechanical, electrical, or fluidic.

References herein to the positions of elements (e.g., “top,” “bottom,”“above,” “below”) are merely used to describe the orientation of variouselements in the FIGURES. It should be noted that the orientation ofvarious elements may differ according to other exemplary embodiments,and that such variations are intended to be encompassed by the presentdisclosure.

The hardware and data processing components used to implement thevarious processes, operations, illustrative logics, logical blocks,modules and circuits described in connection with the embodimentsdisclosed herein may be implemented or performed with a general purposesingle- or multi-chip processor, a digital signal processor (DSP), anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA), or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. A generalpurpose processor may be a microprocessor, or, any conventionalprocessor, controller, microcontroller, or state machine. A processoralso may be implemented as a combination of computing devices, such as acombination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration. In some embodiments, particularprocesses and methods may be performed by circuitry that is specific toa given function. The memory (e.g., memory, memory unit, storage device)may include one or more devices (e.g., RAM, ROM, Flash memory, hard diskstorage) for storing data and/or computer code for completing orfacilitating the various processes, layers and modules described in thepresent disclosure. The memory may be or include volatile memory ornon-volatile memory, and may include database components, object codecomponents, script components, or any other type of informationstructure for supporting the various activities and informationstructures described in the present disclosure. According to anexemplary embodiment, the memory is communicably connected to theprocessor via a processing circuit and includes computer code forexecuting (e.g., by the processing circuit or the processor) the one ormore processes described herein.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure may be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, orother optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Combinationsof the above are also included within the scope of machine-readablemedia. Machine-executable instructions include, for example,instructions and data which cause a general purpose computer, specialpurpose computer, or special purpose processing machines to perform acertain function or group of functions.

Although the figures and description may illustrate a specific order ofmethod steps, the order of such steps may differ from what is depictedand described, unless specified differently above. Also, two or moresteps may be performed concurrently or with partial concurrence, unlessspecified differently above. Such variation may depend, for example, onthe software and hardware systems chosen and on designer choice. Allsuch variations are within the scope of the disclosure. Likewise,software implementations of the described methods could be accomplishedwith standard programming techniques with rule-based logic and otherlogic to accomplish the various connection steps, processing steps,comparison steps, and decision steps.

It is important to note that the construction and arrangement of thedoor systems and the components thereof as shown in the variousexemplary embodiments is illustrative only. Additionally, any elementdisclosed in one embodiment may be incorporated or utilized with anyother embodiment disclosed herein. Although only one example of anelement from one embodiment that can be incorporated or utilized inanother embodiment has been described above, it should be appreciatedthat other elements of the various embodiments may be incorporated orutilized with any of the other embodiments disclosed herein.

1. A locking system comprising: a server; an electronic lockingmechanism; and a controller associated with a user, the controllerconfigured to: detect the electronic locking mechanism and acquire lockdata therefrom; and transmit the lock data to the server; wherein theserver, without requiring interaction from the user, is configured to:receive the lock data for the electronic locking mechanism; register theelectronic locking mechanism to the user; and transmit an accesscredential for accessing the electronic locking mechanism to a userdevice associated with the user; and wherein the electronic lockingmechanism is configured to: receive the access credential directly fromthe user device or indirectly from the user device through thecontroller; and make an access decision based on the access credential,independent of the server.
 2. The locking system of claim 1, wherein thecontroller includes (i) a first transceiver configured to receive firstsignals from the electronic locking mechanism in a first communicationprotocol and (ii) a second transceiver configured to receive secondsignals from at least one of the user device or the server in a secondcommunication protocol, and wherein the controller is configured tooperate as a bridge that converts (i) the first signals received in thefirst communication protocol to first converted signals transmitted inthe second communication protocol and (ii) the second signals receivedin the second communication protocol to second converted signalstransmitted in the first communication protocol.
 3. The locking systemof claim 2, wherein the first communication protocol is a Bluetoothcommunication protocol and the second communication protocol is at leastone of a Wi-Fi communication protocol or a cellular communicationprotocol.
 4. The locking system of claim 2, wherein the controllercommunicates with the at least one of the server or the user devicethrough an intermediary device.
 5. The locking system of claim 1,wherein the electronic locking mechanism is installable within a doorand the controller is separate from the door.
 6. The locking system ofclaim 1, wherein the controller and the electronic locking mechanism areinstallable within a door.
 7. The locking system of claim 1, wherein theelectronic locking mechanism is installable within a door.
 8. Thelocking system of claim 7, further comprising the door, wherein the doorincludes a first connection box embedded therein, wherein the firstconnection box includes a first interface, wherein the electroniclocking mechanism includes a connector, and wherein the controller isconfigured to detect the electronic locking mechanism in response to theconnector engaging with the first interface.
 9. The locking system ofclaim 8, further comprising: an electric transfer hinge coupled to anedge of the door, the electric transfer hinge configured to (i)facilitate pivotally coupling the door to a door jamb and (ii)facilitate electrically coupling the electronic locking mechanism to anexternal power source; and a second connection box embedded in the door;wherein the second connection box includes a second interface configuredto selectively interface with a second connector of the electrictransfer hinge; and wherein the first connection box is electricallycoupled to the second connection box.
 10. The locking system of claim 7,wherein the electronic locking mechanism is an electronic deadbolt. 11.The locking system of claim 7, wherein the electronic locking mechanismis an electronic strike plate.
 12. A locking system comprising: aserver; and a controller associated with a user; wherein the controlleris configured to: detect an electronic locking mechanism and acquirelock data therefrom; and transmit the lock data to the server; andwherein the server, without requiring interaction from the user, isconfigured to: receive the lock data for the electronic lockingmechanism; register the electronic locking mechanism to the user; andtransmit an access credential for accessing the electronic lockingmechanism to a user device associated with the user.
 13. The lockingsystem of claim 12, wherein the controller includes (i) a firsttransceiver configured to receive first signals from the electroniclocking mechanism in a first communication protocol and (ii) a secondtransceiver configured to receive second signals from at least one ofthe user device or the server in a second communication protocol, andwherein the controller is configured to operate as a bridge thatconverts (i) the first signals received in the first communicationprotocol to first converted signals transmitted in the secondcommunication protocol and (ii) the second signals received in thesecond communication protocol to second converted signals transmitted inthe first communication protocol.
 14. The locking system of claim 13,wherein the first communication protocol is a Bluetooth communicationprotocol and the second communication protocol is at least one of aWi-Fi communication protocol or a cellular communication protocol. 15.The locking system of claim 13, wherein the controller communicates withthe at least one of the server or the user device through anintermediary device.
 16. A method for automatically registering anelectronic locking mechanism, the method comprising: detecting, by acontroller, the electronic locking mechanism, wherein the controller isassociate with a user; acquiring, by the controller, lock data from theelectronic locking mechanism; transmitting, by the controller, the lockdata to a server; receiving, by the server, the lock data the electroniclocking mechanism; registering, by the server, the electronic lockingmechanism to the user; transmitting, by the server, an access credentialfor accessing the electronic locking mechanism to a user deviceassociated with the user; receiving, by the electronic lockingmechanism, the access credential directly from the user device orindirectly from the user device through the controller; and making, bythe electronic locking mechanism, an access decision based on the accesscredential.
 17. The method of claim 16, wherein the controllercommunicates with at least one of the server or the user device throughan intermediary device.
 18. The method of claim 16, wherein theelectronic locking mechanism is installable within a door and thecontroller is separate from the door.
 19. The method of claim 16,wherein the electronic locking mechanism is installable within a door.20. The method of claim 19, wherein the door includes a connection boxembedded therein, wherein the connection box includes a lock interface,wherein the electronic locking mechanism includes a connector, andwherein the controller detects the electronic locking mechanism inresponse to the connector engaging with the lock interface.